Skip to main content
Glama

One analysis

get_analysis
Read-only

Your saved analysis structure, without model interpretation. Free.

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": {
      "id": "<id>"
    },
    "name": "get_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description does add two genuine behavioral facts beyond that: the response is raw structure with no model interpretation, and the call is free. It still omits what happens when the ID is unknown (empty vs error) and whether the payload is large.

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

Conciseness3/5

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

Two short fragments, so nothing is wasted, and the resource is front-loaded. But "Free." as a standalone sentence and the unexplained phrase "without model interpretation" read as under-specification rather than tight writing.

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

Completeness2/5

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

With no output schema, the description is the only place to explain the return shape, and it does so only as "analysis structure, without model interpretation." Combined with an undocumented required ID and no differentiation from get_structure, an agent cannot confidently predict the response or choose this tool over its siblings.

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

Parameters2/5

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

There is one required parameter, id, and schema description coverage is 0% — the schema gives only a UUID pattern and no meaning. The description never mentions the ID, so it does not compensate for the gap; the agent must infer that the argument selects which saved analysis to fetch.

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?

"Your saved analysis structure" names a resource but never states the verb or the scope — it does not say it retrieves a single analysis by ID, and the title "One analysis" carries that load instead. It is distinguishable from list_analyses in spirit, but against the sibling get_structure it is unclear which one returns the saved analysis versus the underlying structure.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given, and no alternative is named. "Free" hints that this call has no cost, which is a weak usage signal at best and is never tied to a decision about which sibling to pick.

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