Skip to main content
Glama

Get a saved quote

get_quote
Read-onlyIdempotent

A quote from generate_quote by id, with its render status and the image once the render is done.

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_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe 24-character quote id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/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 safety is covered. The description still adds real behavioral context beyond them: the return includes a render status and the image only once rendering is done, which signals an asynchronous lifecycle and that a call may legitimately return incomplete results. It does not cover error or not-found behavior, keeping it short of a 5.

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?

One compact sentence with no filler, and the identifying detail (the id lookup, the source tool) comes first. The phrasing is slightly compressed and grammatically fragmentary, but nothing is wasted and nothing important is buried.

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 one required parameter, no output schema, and full annotation coverage, the description fills the gaps that matter: what is returned (render status and image) and the condition under which the image appears. Only minor operational details, such as behavior when the quote is missing or unpublished, are absent.

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 coverage is 100% and the single id parameter is already documented in the schema as a 24-character quote id. The description only restates 'by id' and links that id to what generate_quote produced, adding marginal meaning. Baseline 3 is appropriate when the schema carries the parameter documentation.

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 names a specific resource (a quote), the lookup key (by id), and the originating sibling (generate_quote), so an agent can tell it apart from generate_quote or request_quote. It is written as a sentence fragment ('A quote from generate_quote by id') rather than a verb phrase, which slightly weakens the action signal, but the retrieval intent is unmistakable.

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 rather than stated: the agent can infer this fetches an existing quote rather than creating a new one, which is enough to choose it over generate_quote. There is no explicit when-to-use or when-not-to-use guidance, and nothing about whether this is the right tool to poll repeatedly or when to fall back to another sibling.

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