Skip to main content
Glama

Agent spotlight

agent_spotlight
Read-onlyIdempotent

Pin your AI agent, MCP server, x402 API, or micro-bounty on the live APEX Global Agent Spotlight Wire (https://apexfaucet.xyz/memory/ + GET /api/spotlight/feed) for 24 hours. Auto-verifies HTTPS/anti-phishing safety via url-threat-check, issues an Ed25519 SpotlightCertificate, and announces on Telegram. $0.01 per 24h pin over x402 or X-API-Key.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTPS URL of the agent, MCP server, or API.
nameYesAgent, MCP server, or API name (2-64 chars).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).
taglineYesShort pitch or capability description (5-180 chars).
categoryNoSpotlight category (default agent).
priceUsdNoOptional per-call price in USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior1/5

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

The description describes a mutating, side-effecting operation: it pins a listing, auto-verifies via url-threat-check, issues an Ed25519 SpotlightCertificate, announces on Telegram, and charges $0.01. The annotations declare readOnlyHint=true and destructiveHint=false, which directly contradicts a tool that creates a public listing and spends money. This is a serious inconsistency an agent could act on incorrectly.

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 action and resource, with no filler. It is dense with endpoints, jargon, and pricing, but every clause carries information an agent needs; the parenthetical URL and feed path are the only slightly cluttered element.

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?

For a six-parameter tool with no output schema, the description covers the side effects (verification, certificate issuance, Telegram announcement) and cost, which is useful. However, it omits what the caller receives back, whether re-pinning the same URL is idempotent, and how authentication is supplied, leaving gaps for a paid mutation.

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 all six parameters, and the baseline is 3. The description adds some meaning by naming x402 and X-API-Key as payment paths and quoting a $0.01/24h price, but it does not clarify how the optional priceUsd parameter differs from that pin fee, which is a real ambiguity.

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 opens with a specific verb and resource: 'Pin your AI agent, MCP server, x402 API, or micro-bounty on the live APEX Global Agent Spotlight Wire ... for 24 hours.' It names the exact surface (URL plus feed endpoint) and the duration, so an agent can tell this apart from every sibling in the catalog, none of which publish listings.

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 implied rather than stated: the description tells you what pinning achieves and what it costs ($0.01 per 24h), but never says when to choose this over alternatives or when not to use it. There is no explicit prerequisite or exclusion guidance beyond the payment mention.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources