Skip to main content
Glama
IEZhu

Agents-Core

by IEZhu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Route to a persona

route_and_load

Routes a user request to the correct specialist persona and loads its instructions, so agents start with the right role or switch roles when needed.

Instructions

Route to a specialist. Call only for initial selection or a needed
specialization change; keep the active role locally on continuations. Pass
protocol_version=2 and current_persona. Returns separate instruction blocks.
ROUTE_REQUIRED needs get_agent_context with the same version and descriptor.
Explicit known roles can be loaded directly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe user request to route.
chat_historyNoOptional relevant earlier conversation facts, as a JSON array of strings.
current_personaNoThe `persona` object of the last SUCCESS/NO_CHANGE, copied verbatim; omit or null on first activation. All 7 keys: agent, activation_id, bundle_revision (64 hex characters), scope, skills_loaded, implants_loaded, rules_loaded.
protocol_versionNoPersona protocol version; always 2.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv26.10.14+1807

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare a non-read-only, non-idempotent, non-destructive local operation, so the bar is lowered; the description still adds real behavior: the ROUTE_REQUIRED outcome and its required recovery call, the fact that separate instruction blocks are returned, and the protocol version contract. It does not say what state is mutated or whether repeated routing re-activates a persona, which would round this out.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the purpose and then the usage constraint, with zero filler. The telegraphic naming style ("ROUTE_REQUIRED") is dense but each sentence carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be enumerated, and the description still notes the instruction-block return. It covers the routing protocol, the persona handoff, and the ROUTE_REQUIRED branch, leaving only the mutation/lifecycle detail unspecified for a 4-parameter, nested-object tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the nested current_persona shape and protocol_version are already fully documented. The description only restates "pass protocol_version=2 and current_persona" without adding format or edge-case meaning beyond the schema, which is the baseline 3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Route to a specialist") and adds what comes back ("Returns separate instruction blocks"), so the agent understands this selects/activates a persona. It does not directly contrast itself with nearby siblings like refresh_persona_context or load_implants, though it does name get_agent_context in the error path.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ("initial selection or a needed specialization change"), explicit when-not ("keep the active role locally on continuations"), and a named follow-up tool with the condition that triggers it ("ROUTE_REQUIRED needs get_agent_context with the same version and descriptor"). Alternative of loading explicit known roles directly is also given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools