Skip to main content
Glama
Sign In

Close Knit

by com.getcloseknit
OverviewDiscussionsAdmin

Fetch

fetch
Read-onlyIdempotent

For deep research: one search result by id as text with its page url to cite (an area: every section's headline facts, caveats, sources; a guide: its article). In chat prefer get.

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[id] an id from search results: uk:lsoa:…, uk:msoa:…, uk:lad:…, pc:…, school:…, guide:crime

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent fetch. The description adds useful behavioral context by explaining that the result comes back as text with its page URL for citation, and by describing what an area versus a guide contains. The remaining gap is minor because the output schema exists and annotations cover the safety profile.

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?

The definition is a single front-loaded sentence that leads with the deep-research use case. The parenthetical detail about area and guide output earns its space by clarifying what text content the caller receives.

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 one-parameter read tool with full schema coverage, annotations, and an output schema, the description is complete. It covers when to use it, the alternative to prefer in chat, and what kind of text result to expect.

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 description coverage is 100%, so the id parameter and its accepted formats are already documented. The description reinforces that the id must come from search results and that exactly one result is fetched, but it does not add substantial syntax or format detail beyond the schema.

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: fetch one search result by id as text with its page URL to cite. It also distinguishes this tool from the sibling get by reserving it for deep research rather than chat use.

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?

It gives explicit usage guidance: use this for deep research, and prefer get in chat. The alternative is named directly, so an agent can choose between them without opening either schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Close Knit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources