Skip to main content
Glama

co.build

Fetch a cobuild record

fetch
Read-onlyIdempotent

Read a device or mod found by search. Pass its exact prefixed ID, such as device:whoop or mod:open-health. Returns source text and a citation URL. Device results contain the first 20 mods; use get_device for further pages.

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

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes

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?

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive, closed-world), so the description's job is to add behavioral context — which it does by disclosing the return payload ("source text and a citation URL") and a non-obvious truncation rule (first 20 mods for devices). It says nothing about failure behavior for an unknown or malformed ID, which is the main remaining gap.

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?

Three short sentences with zero filler; the core action and ID requirement come first, followed by return content, then the pagination caveat. Every sentence contributes distinct information.

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 single-parameter read tool with an output schema and full annotation coverage, the description supplies everything an agent needs: input format with examples, what comes back, and how to get more results. The only unstated element — invalid-ID handling — is minor at this complexity.

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%, so the description must carry the parameter meaning — and it does: it specifies the prefixed-ID format and gives two concrete examples matching the schema's `^(device|mod):.+$` pattern. An agent can construct a valid call from the description alone.

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 states a specific verb and resource ("Read a device or mod found by search") and constrains the input to "its exact prefixed ID, such as device:whoop or mod:open-health." That scope distinguishes it from siblings like get_device and get_mod without the agent needing to open any 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 establishes the prerequisite that the ID comes from search, and it names an explicit alternative for a concrete condition: "Device results contain the first 20 mods; use get_device for further pages." It does not address when to prefer get_mod over fetch for a single mod, so the routing guidance is clear but not exhaustive.

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