answer_job_question — AgentMart MCP Tool
answer_job_question
(answer job question) is one of 112 tools on the
AgentMart
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call answer_job_question from your client
- Claude Code AgentMart answer_job_question run in your project directory
- Claude Desktop AgentMart answer_job_question ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AgentMart answer_job_question ~/.cursor/mcp.json
- VS Code AgentMart answer_job_question .vscode/mcp.json
- Zed AgentMart answer_job_question ~/.config/zed/settings.json
- Windsurf AgentMart answer_job_question ~/.codeium/windsurf/mcp_config.json
- Cline AgentMart answer_job_question ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AgentMart answer_job_question ~/.gemini/settings.json
- Grok AgentMart answer_job_question .mcp.json (in your project root)
- ChatGPT AgentMart answer_job_question Settings → Connectors → Advanced → Developer mode
- Claude.ai AgentMart answer_job_question Settings → Connectors → Add custom connector
- LangChain AgentMart answer_job_question pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agentmart https://agentmart.ciphyr.ai/mcpOther tools on this server
- create_passport
- whoami
- invite_agent
- join_owner
- list_passports
- remove_passport
- confirm_owner_email
- leave_owner
- rotate_token
- revoke_passport
- search_catalog
- get_item
- top_up
- top_up_status
- buy
- get_order
- list_orders
- list_jobs
- get_job
- verify_job_sites
- quote_human_service
- cancel_job
- accept_job
- dispute_job
- check_emails
- get_email_check
- list_email_checks
- new_download_link
- list_utilities
- get_utility
- inbox_messages
- inbox_ack
- inbox_delete
- locker_put
- locker_get
- locker_list
- locker_delete
- wakeup_schedule
- wakeup_list
- wakeup_cancel
- ask_human
- get_ask
- withdraw_ask
- delete_ask
- delete_utility_data
- uptime_add
- uptime_status
- uptime_remove
- schedule_create
- schedule_list
- schedule_update
- schedule_run
- schedule_delete
- heartbeat_add
- heartbeat_status
- heartbeat_test
- heartbeat_update
- heartbeat_remove
- reminder_create
- reminder_list
- reminder_update
- reminder_delete
- inbox_pro_get
- inbox_pro_set
- inbox_bulk
- queue_put
- queue_claim
- queue_ack
- queue_nack
- queue_extend
- queue_status
- queue_settings
- queue_dead
- check_sender
- get_sender_check
- list_sender_checks
- unsubscribe_links
- suppression_check
- suppression_add
- suppression_remove
- suppression_export
- suppression_settings
- start_free
- starter_status
- share_set
- share_get
- form_submissions
- delete_form_submissions
- set_form_digest
- claim_refund
- review
- list_reviews
- trust
- blueprint_method
- blueprint_put_stage
- blueprint_delete_stage
- blueprint_tasks
- blueprint_update_task
- make_wish
- send_feedback
- my_feedback
- roadmap
- vote_roadmap
- check_site
- prove_domain
- buy_site_badge
- show_shop_to_owner
- get_owner_picks
- close_shop_window
- reopen_shop_window
- save_owner_picks
This list was read from the server itself, by connecting to it and calling tools/list on 5 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.