Skip to main content
Glama
Sign In

TransformPipe

by io.github.raudarlabs
OverviewDiscussionsAdmin

Summarise a document

tp_summarize_document

Generates a summary of one document — a paragraph on what it is and what it concludes, then a short list of its specifics — and caches it on the account. Use it when the user asks for a summary or an overview of a saved document. The document's text is sent to Google's Gemini API to write the summary. A cached summary is returned without calling the model again unless force: true is passed. Summaries have their own daily limit per account.

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

Input Schema

NameRequiredDescriptionDefault
idYesDocument id from tp_list_documents.
forceNoGenerate a new summary even when one is cached. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare non-destructive, non-readonly, open-world behavior; the description adds materially important context the annotations cannot: document text is sent to Google's Gemini API, results are cached on the account, cached results skip the model call unless force: true, and summaries have a per-account daily limit. These are exactly the side effects, data-egress and quota facts an agent needs, and they are consistent with idempotentHint=false and openWorldHint=true.

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?

Front-loaded with purpose and output shape before usage guidance, then the operational caveats (data egress, caching, quota). Every sentence carries distinct information — no filler, no repetition of the name or annotations.

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?

There is no output schema, and the description compensates by describing the returned summary's structure. With only two parameters, full schema coverage, and caveats covering caching, third-party processing and rate limits, an agent has everything needed to call this correctly and set expectations with a user.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by linking `force` to the cache-and-model-call tradeoff (a cached summary is returned without paying for a model call unless force is true). The `id` parameter's provenance is left entirely to the schema's reference to tp_list_documents.

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 ("Generates a summary of one document") and goes further to define the exact output shape — a paragraph on what it is and concludes, plus a short list of specifics. This clearly separates it from siblings like tp_get_document or tp_search_documentation without needing to open the 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?

"Use it when the user asks for a summary or an overview of a saved document" gives an explicit trigger condition, and the implicit contrast with retrieval siblings is clear. It stops short of naming an alternative or stating when not to use it (e.g. for a live/unsaved document), so it is strong but not exhaustive.

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

All TransformPipe 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