Tool names and compatibility

Use the veryfront__ prefix when discovering or calling platform tools.

Canonical names

Veryfront platform tools use canonical names such as veryfront__list_projects and veryfront__get_file. Integration namespaces such as github__ and gmail__ stay unchanged. Project tools keep their exact names. The MCP tool reference lists every tool under its canonical name.

tools/call requires the veryfront__ name for a platform tool. An unprefixed platform name, such as list_projects, answers the JSON-RPC error -32602 before the call runs. GET /mcp/tools/{tool_name} answers 404 for an unprefixed name.

Canonical agent-reference discovery uses tool_names: "canonical" on veryfront__list_agent_tool_references. Its platform results include legacy_name to identify the stored selector. Submit the returned name when selecting a new tool so the API can validate its owner before storing the compatible selector. Keep untouched saved selectors unchanged. Ambiguous project and platform identities are rejected instead of silently selecting a different tool.

Existing clients

The ?tool_names=legacy and ?tool_names=canonical URL selectors and the params._meta["veryfront/tool-names"] hint no longer change discovery: every connection lists the canonical names. To migrate a client that calls unprefixed names, add the veryfront__ prefix to each platform tool name it calls.

The former run tools are removed. Use their canonical replacements:

Removed toolUse instead
get_agent_runveryfront__get_run
list_agent_runs, get_active_agent_runveryfront__list_conversation_runs
list_run_children, list_child_agent_runs, list_child_agent_runs_by_parent_runveryfront__list_run_child_runs
list_child_agent_runs_by_parent_conversationveryfront__list_conversation_child_runs
list_schedule_runsveryfront__list_runs
submit_run_resume_signalveryfront__resume_run
submit_input_request_response, submit_run_input_response, submit_conversation_input_request_responseveryfront__create_input_response
get_run_input_request, get_conversation_input_requestveryfront__get_input_request
get_agent_run_eventsveryfront__list_run_events
get_agent_run_snapshotveryfront__get_run_snapshot
get_run_event_summaryveryfront__get_run_events_summary
search_project_tracesveryfront__list_project_traces
list_input_requestsveryfront__list_conversation_input_requests
create_input_requestveryfront__create_run_input_request
cancel_conversation_input_requestveryfront__cancel_input_request

Next

Connect an MCP client to make your first call.

The MCP reference lists tool arguments and access requirements.