Skip to main content
Glama

agent_advisor

Read-onlyIdempotent

AI help desk: which analysis fits your question, interpreting results, fixing errors. Multi-turn.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "question": "<question>"
    },
    "name": "agent_advisor"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYesYour question or request

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / message
      Removed value: -{
      -  "description": "Your question or request",
      -  "type": "string"
      -}
    • addedInput schema / properties / question
      Added value: +{
      +  "description": "Your question or request",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "message"
      -]New value: +[
      +  "question"
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description's one genuinely additive signal is 'Multi-turn', which tells the agent the conversation can be continued across calls — but it does not say whether state persists across separate tool calls, how the advisor's answers are shaped, or anything about latency or limits.

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?

Three short fragments and a trailing qualifier — nothing is padded or redundant. It is front-loaded and scannable, though the telegraphic style costs some readability in exchange for brevity.

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?

For a one-parameter, read-only advisory tool, the essentials are present: what it is for, the three use cases, and the fact that it is conversational. With no output schema present, the missing piece is any hint of what the advisor returns (a recommendation, a tutorial, a diagnostic), but the bar is low for a tool this simple.

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?

There is a single parameter, 'question', fully documented in the schema at 100% coverage. The description adds nothing about how to phrase it, whether context from earlier turns should be repeated, or how much detail helps — so per the baseline rule with high schema coverage, a 3 is appropriate.

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

Purpose3/5

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

The description frames the tool as an 'AI help desk' for three jobs: choosing which analysis fits a question, interpreting results, and fixing errors. That is a recognizable purpose, but it is expressed in compressed fragments rather than a clear verb+resource statement, and it does not distinguish the tool from near-neighbors like check_tool_fit, discover_tools, or ask_library that appear in the sibling list.

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

Usage Guidelines3/5

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

Usage is implied by the three listed scenarios (picking an analysis, interpreting output, fixing errors), which gives an agent a reasonable sense of when to reach for it. However, no alternative is named and no 'when not to use' condition is given, so the agent must infer the boundary with check_tool_fit and ask_library on its own.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.