Skip to main content
Glama
swarm-agent-operator

swarm-x402-mcp

by swarm-agent-operator
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

One-page web research brief

summary

Researches any topic on the live web and returns a one-page brief with linked sources, paid per call in USDC on Base.

Instructions

A one-page brief on a topic, researched on the live web at request time, sources linked. Price: $0.75 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.9/5.0
Behavior5/5

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

The description discloses far more than the annotations: it makes a network call, requires SWARM_WALLET_KEY, costs $0.75 per call in USDC on Base via x402, checks the live quote against SWARM_MAX_USD before paying, and charges only on success. Preconditions, side effect, and billing semantics are all explicit.

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?

Front-loaded with the purpose in the first sentence, then price, then payment mechanics. The parenthetical is dense but each clause (wallet key, quote check, charge-on-success) carries distinct, decision-relevant information rather than padding.

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?

With no output schema, the description still conveys the return shape (one-page brief, linked sources) and the key risk (paid call). Minor gaps remain: error/failure behavior, latency, and freshness of the live research are not addressed.

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%, so the schema already documents topic, context, and requirements. The description adds no parameter-level meaning beyond that, which is the correct baseline of 3 when the schema does the heavy lifting.

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 specific deliverable ("a one-page brief on a topic"), how it's produced ("researched on the live web at request time"), and what comes back ("sources linked"). It is clear on its own, but it never distinguishes itself from the sibling "report", which could plausibly be confused with a research brief.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer it should call this when it needs a researched web brief. There is no explicit when-to-use versus alternatives (e.g. report), no when-not to call, and no guidance on reusing results to avoid repeat charges.

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