Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Open a saved lookup

research_saved_get
Read-onlyIdempotent

The full saved result of one paid lookup (ids come from research_saved), exactly as it was returned then. 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": {
      "siteId": "<siteId>",
      "id": "<id>"
    },
    "name": "research_saved_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
siteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds genuinely new facts -- the result is a frozen snapshot 'exactly as it was returned then' and the call costs nothing -- which go beyond the annotations. It does not describe pagination or size limits of the returned payload, keeping it at a solid 3.

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

Conciseness5/5

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

A single sentence with a parenthetical that earns its place by naming the id source; the two key facts (what you get, and that it is free) are front-loaded with zero filler.

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 simple two-param read tool with rich annotations, the description covers what is returned (the full saved result, unchanged since capture), where the id comes from, and the cost. The only real gap is the unexplained siteId parameter.

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?

Schema description coverage is 0%, so the description carries the full burden. It clarifies only one parameter, id (sourced from research_saved, max 40 chars per schema), and says nothing about siteId, which is also required. Half the parameters remain semantically opaque.

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?

The description specifies the resource precisely: it returns the full saved result of one paid lookup, and it names the sibling (research_saved) where the id originates, so an agent can distinguish it from the listing tool. It is a noun phrase rather than a verb-led statement, but the operation (retrieve one saved result) is unambiguous.

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?

It implies the workflow by stating that ids come from research_saved, and it notes the call is 'Free', which is useful cost context. However, there is no explicit when-not-to-use guidance or statement of what happens if the id is stale or from another site.

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