Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

ads_browse

Browse all live x402ads ad slots across the agentic web, including property, format, audience, and price tiers; see inventory other agents registered.

Instructions

Browse x402ads: the ad network for the agentic web. Lists every live slot (property, format, audience, price tiers) across the network, including slots other agents have registered. Free. Buy with POST https://x402-agent-pay.com/x402ads/buy (x402 USDC on Base L2) or register your own site's inventory with ads_register_slot.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ads_browse"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that the call is 'Free' and that results include slots registered by other agents, which is meaningful cost/scope context. It omits any statement about authentication, rate limits, pagination, or freshness of the 'live' listing, which are the traits an agent would need for a network-wide listing call.

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?

Three short sentences, front-loaded with the core action and the returned fields; the payment URL and register pointer are actionable rather than filler. Slightly overstuffed with commercial routing for a browse tool, but nothing is truly wasteful.

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

Completeness3/5

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

There is no output schema and no annotations, so the description must stand alone; it does well on scope and cost but leaves the sole parameter and the response shape (pagination, ordering, slot count) undocumented. Adequate to call the tool, incomplete for calling it precisely.

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 coverage is 0% for the single 'limit' parameter, and the description never mentions it, so the agent gets no explanation of what the limit bounds (slots returned? price tiers?) or what happens at the default of 30. With a 0%-covered parameter the description should compensate, and it does not.

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?

States a specific verb and resource ('Browse x402ads... Lists every live slot') and enumerates the returned fields (property, format, audience, price tiers), which lets an agent distinguish this from siblings like ads_register_slot or marketplace_browse without opening the schema.

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?

Gives a clear when-to-use context (finding live inventory) and explicitly routes two downstream actions to other tools: buying via the x402 POST endpoint and listing inventory via ads_register_slot. It does not state any exclusions or when NOT to browse, and offers no guidance on choosing between this and other marketplace browse tools.

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