Skip to main content
Glama

Fetch a result (ChatGPT-compatible)

fetch
Read-onlyIdempotent

For ChatGPT connectors and deep research only; other clients use get_vendor. Opens one id returned by search (a vendor, a price summary or a cost page) as plain text with the URL to cite, in the shape ChatGPT expects. To look up a vendor by name, URL or slug without searching first, use get_vendor, which returns the same facts as structured fields.

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
idYesAn id from search, e.g. "vendor:448-studio" or "price:djs:brooklyn".

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
metadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/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, destructiveHint=false), and the description adds genuinely new behavior: output is plain text in the shape ChatGPT expects, including a citable URL, rather than structured fields. It doesn't state what happens with a stale or invalid id, which is the remaining behavioral gap.

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?

Three sentences, front-loaded with the client restriction that determines whether an agent should call it at all, followed by the return shape and the alternative. Dense but every clause carries routing or output information; the parenthetical id-type list is the only slightly bulky element.

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 single-parameter read tool with an output schema and full annotation coverage, the description supplies what structured fields can't: client compatibility, plain-text-with-URL return shape, and the sibling to use instead. Missing only failure behavior on invalid ids.

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 id property already documents the namespace prefixes and gives examples. The description only reinforces that the id must come from search, adding little beyond the schema; baseline 3 applies.

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?

States a specific verb and resource ('opens one id returned by search') and enumerates what that id can resolve to (a vendor, a price summary or a cost page), which distinguishes it from search and get_vendor without opening either schema.

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

Usage Guidelines5/5

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

Explicitly scopes the audience ('ChatGPT connectors and deep research only') and names the alternative for everyone else ('other clients use get_vendor'). It also gives a second routing rule: to look up a vendor by name, URL or slug without searching first, use get_vendor.

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