Skip to main content
Glama
Sign In
boltwork-mcp

boltwork-mcp

by Squidboy30
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

trial_summarise

Summarise up to 1000 characters of text to get a title, summary, key points, sentiment, and topics. Free trial with no Lightning wallet required, limited to 5 calls per hour.

Instructions

FREE trial text summarisation — no Lightning wallet required. Summarises up to 1000 characters of text. Returns title, summary, key points, sentiment, and topics. Rate limited to 5 calls per hour per IP. Use this to try Boltwork before setting up a wallet. For full PDF/webpage summarisation, use summarise_pdf or summarise_webpage.

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

Input Schema

NameRequiredDescriptionDefault
textYesText to summarise (max 1000 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.22

TDQS

A4.9/5.0
Behavior5/5

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

Discloses key behaviors: free trial, no wallet required, rate limit (5 calls per hour per IP), max 1000 characters, and output fields (title, summary, key points, sentiment, topics). No annotations provided, so description fully compensates.

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?

Three sentences, each serving a distinct purpose: trial offer, constraints, output details, and alternatives. Front-loaded with key info ('FREE'). No wasted words.

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 simple tool with one param and no output schema, the description covers purpose, usage constraints, rate limits, and output format completely. No gaps.

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% with clear description of 'text' parameter including max length. Description adds context about output fields and trial context, slightly enhancing schema. Baseline 3 plus extra value.

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?

Clearly states it is a free trial text summarisation tool with specific action (summarise) and resource (text). Differentiates from sibling tools like summarise_pdf and summarise_webpage by specifying scope (up to 1000 chars) and trial nature.

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?

Explicitly says when to use: 'Use this to try Boltwork before setting up a wallet.' Mentions alternatives and provides context on rate limits and prerequisites (no wallet needed).

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

Deploy Server

Other Tools