Skip to main content
Glama

Tolca: business verification (KYB)

summarize

summarize
Read-onlyIdempotent

Summarize long text into a tight, faithful summary. Input: text (up to 40k chars), optional max_words and language. Costs $0.03 USDC per call (x402 v2, Base or Solana). Send the HTTP header PAYMENT-SIGNATURE with your x402 payment, or call POST https://tolca.tonbot.ca/v1/summarize with an x402 client.

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": {
      "text": "<text>"
    },
    "name": "summarize"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to summarize (up to 40,000 characters)
languageNoLanguage of the summary: auto (same as the text), en or fr
max_wordsNoMaximum length of the summary in words (20 to 1,000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / language / description
      Added value: +"Language of the summary: auto (same as the text), en or fr"
    • addedInput schema / properties / max_words / description
      Added value: +"Maximum length of the summary in words (20 to 1,000)"
    • addedInput schema / properties / text / description
      Added value: +"Text to summarize (up to 40,000 characters)"
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: a per-call cost of $0.03 USDC, the x402 v2 payment scheme, accepted chains (Base or Solana), and the required PAYMENT-SIGNATURE header. It does not mention rate limits, failure/refund behavior on failed calls, or that the text leaves the local environment, which is notable given openWorldHint.

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 purpose before operational details, with no filler. The payment sentence is dense but every clause carries information an agent cannot get elsewhere. Slightly long for the value delivered relative to a purely descriptive opening.

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

Completeness3/5

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

There is no output schema, so the description is the only place an agent could learn the return shape, and it does not say what comes back (summary string plus fields? metadata?). It also omits data-handling implications of an open-world, paid call. The credit is that it does fully cover the unusual prerequisite here, namely payment setup, which is the biggest barrier to a successful invocation.

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 schema alone already documents text, language and max_words with bounds and the enum values. The description only restates the character limit and names the two optional parameters, adding no syntax, default or interaction detail beyond the schema. This is the expected baseline when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Summarize long text into a tight, faithful summary,' with the qualifiers 'tight, faithful' signaling the expected output quality. It is clearly distinct from sibling tools like translate or extract, though it never states that distinction explicitly. An agent can tell what the tool does without opening 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 Guidelines3/5

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

Usage context is implied by 'Summarize long text' and by the 40k character bound, so an agent can infer this is for long-form input rather than short strings. However, there is no explicit when-to-use versus when-not guidance and no comparison to alternatives such as translate or extract. The bulk of the practical guidance concerns payment mechanics rather than task selection.

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.