Skip to main content
Glama
swarm-agent-operator

swarm-x402-mcp

by swarm-agent-operator
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Full web research report

report

Research any topic live on the web and generate a sourced Markdown document. Paid per call.

Instructions

A full Markdown report on a topic, researched on the live web at request time, sources linked. Price: $0.99 per call. Calls SWARM's shop over the network and, with SWARM_WALLET_KEY set, pays in USDC on Base via x402 (the live quote is checked against SWARM_MAX_USD before paying; charged only on success).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesWhat to research
contextNoWhy you need it, or what you already know
requirementsNoAnything the result must cover

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / context / description
      Previous value: -"Optional background you already have."New value: +"Why you need it, or what you already know"
    • changedInput schema / properties / requirements / description
      Previous value: -"Optional format or angle to follow."New value: +"Anything the result must cover"
    • changedInput schema / properties / topic / description
      Previous value: -"What to research."New value: +"What to research"
    • removedInput schema / properties / topic / minLength
      Removed value: -1
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior5/5

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

With annotations only covering hints (openWorld, non-idempotent, non-destructive), the description carries the real burden and does so well: it discloses the $0.99 per-call price, that it calls an external service over the network, that payment is USDC on Base via x402, that a wallet key is required, that the live quote is checked against SWARM_MAX_USD, and that charging happens only on success. These are exactly the side-effect and auth facts an agent needs before invoking a paid tool.

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?

Two sentences, front-loaded with the deliverable and format, followed by cost and payment mechanics; no filler. Slightly dense toward the end with payment plumbing, but every clause conveys actionable information.

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

Completeness4/5

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

For a paid network tool with no output schema, the description covers the return artifact (full Markdown report with linked sources), cost, auth, and billing semantics. It omits expected latency or failure/refund behavior, which would round it out, but nothing essential to correct invocation is missing.

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% and all three parameters (topic, context, requirements) are documented in the schema, so the baseline of 3 applies. The description adds no further meaning about how 'context' or 'requirements' shape the report, but it does not need to.

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 states a concrete verb+resource: it produces a full Markdown research report on a topic, gathered from the live web with linked sources. That is specific and distinguishable from a plain summarizer, but it never explicitly contrasts itself with the sibling 'summary' tool, so sibling differentiation is only implicit.

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?

There is no explicit when-to-use / when-not-to-use guidance and no alternative tool is named, even though 'summary' is an obvious near-neighbor. The only conditional information is a payment prerequisite (SWARM_WALLET_KEY, SWARM_MAX_USD), which is behavioral rather than a selection guideline.

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