Skip to main content
Glama

Embeddings, Rerank & Speech-to-Text (Tanod)

text_summarize

Read-onlyIdempotent

utilpeek: Summarize a text by picking its key sentences. For paper abstracts use paper_digest; for counts use text_stats. Returns an extractive summary: the most central sentences (or ratio of them) by LexRank, picked verbatim and kept in their original order, with per-sentence scores. It does not paraphrase, shorten or check facts. Typically under 0.5 s. Price: USD 0.003. Free: 10 utilpeek calls per IP per UTC day. The submitted text is never logged or stored. Docs: https://tanod.dev/learn/text-summarization-api.html

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

Input Schema

NameRequiredDescriptionDefault
textYesThe text (at most 200,000 characters).
ratioNoPick this share of the sentences instead (at most 100).
languageNoStop-word language: de, en (default), es, fr, it, nl or pt.en
sentencesNoSentences to pick (ignored when ratio is set).

Output Schema

NameRequiredDescriptionDefault
noteNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
methodNo
sourceNo
summaryNo
sentencesNo
iterationsNo
input_truncatedNo
sentences_totalNo
sentences_selectedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / properties / language / title
      Removed value: -"Language"
    • removedInput schema / properties / ratio / default
      Removed value: -null
    • removedInput schema / properties / ratio / title
      Removed value: -"Ratio"
    • removedInput schema / properties / sentences / title
      Removed value: -"Sentences"
    • removedInput schema / properties / text / title
      Removed value: -"Text"
    • removedInput schema / title
      Removed value: -"text_summarizeArguments"
    • removedOutput schema / properties / sentences / items
      Removed value: -{
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
  2. Changed2 schema fields changed
    • addedInput schema / properties / language / description
      Added value: +"Stop-word language: de, en (default), es, fr, it, nl or pt."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "input_truncated": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "iterations": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "method": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "note": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "sentences": {
      +      "items": {
      +        "type": [
      +          "object",
      +          "null"
      +        ]
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "sentences_selected": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "sentences_total": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "source": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "summary": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description goes further with real behavioral context: extractive only, verbatim, no paraphrasing or fact-checking, sub-0.5s latency, pricing, a 10-call/IP/day free tier, and a no-logging/no-storage privacy guarantee. It does not describe pagination or result size limits, keeping it just short of a 5.

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?

Purpose and the sibling routing are front-loaded, then return semantics, then limits. Every sentence carries information, though the price/free-tier/privacy sentence is somewhat boilerplate for a tool-selection decision and could be tightened.

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 read-only, single-text tool with a fully described 4-param schema and an output schema, nothing an agent needs is missing: scope, method, input bounds (200k chars, max 100 sentences), overrides, latency, cost, and privacy are all stated.

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; the description earns extra by explaining that the picked sentences are the most central by LexRank, kept in original order with per-sentence scores, and that ratio selects a share of sentences as an alternative to a fixed count. That clarifies the sentences-vs-ratio interaction beyond the schema's terse 'ignored when ratio is set'.

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?

"Summarize a text by picking its key sentences" gives a specific verb, resource, and method (extractive LexRank selection), and immediately names the two siblings it is not (paper_digest, text_stats), so an agent can route correctly without opening a 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?

It explicitly says when to use alternatives: paper abstracts go to paper_digest, counting goes to text_stats, leaving summarization here. That is a clear when/when-not split rather than implied usage.

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.