Skip to main content
Glama
ocbenji

@bitcoinbenji/mcp

ai_summarize

Summarize any text into short, medium, or long versions. Each summary costs 20 sats, paid via Lightning.

Instructions

Summarize text (short/medium/long). [20 sats per call]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
max_lengthNomedium
preimageNo(L402 mode) Preimage from paid Lightning invoice — only needed if no API key is set
macaroonNo(L402 mode) Macaroon from the previous 402 challenge
Behavior3/5

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

The description adds cost information ('20 sats per call'), but with no annotations, it fails to disclose other behavioral traits such as idempotency, state modification, or required permissions.

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?

The description is extremely concise (one sentence plus cost note) and front-loaded with the primary action, with no wasted words.

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

Completeness2/5

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

Given 4 parameters, no output schema, and the need to explain L402 payment mode (preimage/macaroon), the description is incomplete and assumes prior knowledge.

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

Parameters2/5

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

Schema covers 50% of parameters with descriptions (preimage, macaroon), but the description does not explain the 'text' or 'max_length' parameters beyond mentioning length options, leaving ambiguity.

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 clearly states the tool's action ('Summarize text') and hints at output length options ('short/medium/long'), distinguishing it from siblings like ai_extract or ai_rewrite.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives (e.g., ai_extract, ai_rewrite), nor are there any exclusions or prerequisites mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ocbenji/bitcoinbenji-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server