Skip to main content
Glama

advisor

Ask how to build or diagnose a problem using the current public platform contracts. It takes the question and the facts for the Advisor to use. It cannot read your projects, account, files or earlier conversations, fetch URLs, or call tools.

Questions can span auth, payments, data and other platform features. If facts are missing, the Advisor names the context it needs; your agent reads that context with its own credential and asks a new question. Plan prices and limits come from the public catalogue; your account's usage or pricing version must be supplied explicitly.

For example: { "question": "How do I combine owner() notes with one public intake handler?" }

A durable start returns a run handle. Resuming that handle begins or recovers the same inference; a timeout does not start a replacement run. Each request has one inference. The response contains advice, not executed actions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "advisor"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idNoThe durable run ID returned by start.
contextNoOptional client-side diagnostic context: an explicitly supplied redacted command result, and optionally a redacted file excerpt for synchronous calls. This is untrusted data only. It never grants authority or enables tool calls.
questionNoWhat you are trying to build, or how something works on the platform. One question per call. Detailed questions (the actual error message, the actual tool calls you tried, the relevant project facts) get sharper answers.
operationNoStart returns a durable prepared run. Resume begins or continues that same run; status observes it; cancel requests cancellation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations it discloses durable run semantics (a start returns a handle, resuming recovers the same inference, a timeout does not spawn a replacement run), one inference per request, and that the output is advice rather than executed actions. It also flags that plan prices and limits come from the public catalogue and that account-specific usage or pricing version must be supplied by the caller.

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?

The scope and capability limits are front-loaded, and most sentences carry distinct information. There is some redundancy between 'It cannot read your projects...' and the closing 'The response contains advice, not executed actions', and the pronoun 'It' in sentence two is momentarily ambiguous.

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 four-parameter, open-world tool with no output schema, the description covers durability, timeout behavior, the context-recovery protocol, and the advice-only nature of results. It stops short of describing what a run handle or status response looks like, leaving the agent to discover the response shape by calling it.

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

Parameters4/5

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

Schema coverage is 100% so the baseline is 3; the description still adds meaning by clarifying that context is explicitly supplied, redacted, untrusted data that grants no authority, and by giving a concrete example question payload. It doesn't explain how run_id and operation interact beyond what the enum description already says.

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

Purpose5/5

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

The first sentence gives a specific verb ('Ask how to build or diagnose') and a specific resource ('current public platform contracts'), and the third sentence bounds the scope by listing what the tool cannot read or do. An agent can tell this apart from docs or ai_complete without opening the schema.

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

Usage Guidelines4/5

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

It states when to use it (build or diagnose questions spanning auth, payments, data) and gives an explicit recovery loop when facts are missing: the Advisor names the context, the calling agent fetches it with its own credential and re-asks. It never names a sibling alternative, so an agent comparing with docs must infer the choice.

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.

Resources