Skip to main content
Glama
Sign In
boltwork-mcp

boltwork-mcp

by Squidboy30
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

summarise_webpage

Summarize any web page by providing its URL. Get title, summary, key points, sentiment, and topics in one request.

Instructions

Summarise any web page by URL. Returns title, summary, key points, content type, sentiment, and topics. Costs 100 sats via Lightning. Use for: articles, blogs, documentation, product pages, news.

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": {
      "url": "<url>"
    },
    "name": "summarise_webpage"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL of the web page to summarise

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.22

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses a behavioral trait ('Costs 100 sats via Lightning') and the output structure. However, it does not mention rate limits, authentication needs, or that the operation is read-only, leaving some gaps.

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?

The description is concise with two sentences. The first sentence conveys the core action and returns; the second adds cost and use cases. Every sentence is valuable with no waste.

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 parameter and no output schema, the description provides a comprehensive list of return fields (title, summary, key points, etc.) and mentions cost. It is sufficient for an agent to understand the tool's output and requirements.

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?

The schema has 100% description coverage for the single 'url' parameter. The description adds contextual value by mentioning the output fields and cost, but does not add new semantics beyond what the schema already provides.

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 'Summarize any web page by URL' and enumerates the output fields (title, summary, key points, etc.), making the tool's purpose specific and distinct from siblings like analyse_image or explain_code.

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?

The description explicitly lists recommended use cases ('Use for: articles, blogs, documentation, product pages, news'), providing good context. However, it does not mention when not to use or compare to alternatives, missing a bit of guidance.

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