Skip to main content
Glama

Fetch a Barmaan document

fetch
Read-onlyIdempotent

Get the full text of one item by the id returned from search (product:, service:, project:, resource:/, category:, certificate:, company:info).

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": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is clear. The description adds useful context beyond annotations by stating that it returns the full text and by specifying accepted id formats; it does not cover error behavior or missing-item handling, which keeps it from 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.

Conciseness5/5

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

It is a single front-loaded sentence with no wasted words. The core action and resource come first, followed by the id source and accepted formats.

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

Completeness5/5

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

For a low-complexity, single-parameter read operation, the description is complete enough to call correctly: it names the input source, enumerates valid id formats, and states that the return value is the item's full text. Annotations already cover the safety behavior, and no output schema is present or needed.

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

Parameters5/5

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

Schema description coverage is 0% and the single parameter is otherwise undocumented, so the description carries the full burden. It does so well by explaining that `id` comes from `search` and by listing concrete identifier forms such as `product:`, `service:`, `project:`, `resource:<kind>/<slug>`, `category:`, `certificate:`, and `company:info`.

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 description uses a specific verb and resource ('Get the full text of one item') and explicitly distinguishes this generic fetch from `search` by requiring an id returned from search. It also enumerates accepted id namespaces, making the tool's purpose unambiguous.

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 clearly establishes the usage context: use this when you have an id returned from `search`. However, it does not explicitly compare against sibling tools such as `get_product`, `get_service`, or `get_resource`, so an agent still has to infer when those are preferable.

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