Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

ads_integrate

Fetch the exact x402ads embed snippet for a registered slot_id as structured data, then paste it into your page to poll every 15 seconds and render the currently paid ad.

Instructions

Fetch the exact embed snippet for an x402ads slot_id (from ads_register_slot) as structured data — no webpage reading required. Paste or inject the returned snippet into your page; it polls every 15s and renders whatever is currently paid for that slot.

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": {
      "slot_id": "<slot_id>"
    },
    "name": "ads_integrate"
  }
}

Input Schema

NameRequiredDescriptionDefault
slot_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does disclose genuinely non-obvious runtime behavior: the returned snippet self-refreshes every 15s and renders whatever is currently paid for that slot, so the response is a stable artifact pointing at dynamic content. It does not say whether unknown slot_ids error, nor the auth/cost profile of the call.

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?

Two tight sentences, front-loaded with the action and return value, followed by the operational instruction to paste/inject the snippet. Every clause carries information: provenance, return form, and runtime behavior.

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 one-parameter read tool with no output schema or annotations, the definition covers the workflow position, return form, and runtime semantics adequately. The main omission is the concrete shape of the 'structured data' response (e.g. whether the snippet is an HTML string or JS fragment).

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 0%, so the description must compensate, and it does by giving the parameter provenance — the slot_id originates from ads_register_slot and identifies an x402ads slot. It does not describe the expected string format (ID vs slug) or failure behavior for malformed values.

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: 'Fetch the exact embed snippet for an x402ads slot_id', and distinguishes itself from its sibling by naming ads_register_slot as the upstream step. The agent knows exactly what it gets back (an embed snippet as structured data) without inspecting 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?

Implies the workflow clearly: get a slot_id from ads_register_slot, then call this tool to obtain the snippet. The phrase 'no webpage reading required' implicitly steers the agent away from scraping an HTML page. It stops short of stating exclusions (e.g. what to do if the slot is unregistered) or prerequisites.

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