Skip to main content
Glama

x420_catalog

Read-only

Retrieves X420's live service catalog, including service IDs, USD prices, input parameters, and deliverables, so you can check costs before calling a paid tool.

Instructions

Free. Fetches X420's live service catalog from https://signature-theme.com/a2a/catalog: every service with its id, price in USD, input parameters and deliverable. Use it to see what the x420_* tools cost before calling one.

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": "x420_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real value beyond them: it is explicitly 'Free', names the external endpoint, says the data is 'live', and enumerates the return contents — which matters since no output schema exists. It stops short of noting response format, size, or error behavior for an open-world network fetch.

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 with the key qualifier ('Free.') front-loaded, followed by what is fetched and why. Every clause carries information; nothing is redundant.

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

Completeness5/5

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

For a zero-parameter read tool with no output schema, the definition supplies the source, the freshness ('live'), the exact returned fields, and the pricing purpose. An agent has everything needed to call it and interpret the result.

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?

There are zero parameters, so the baseline is 4. The description is consistent with that, implying nothing must be supplied, and adds no confusing parameter language.

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 definition gives a specific verb and resource ('Fetches X420's live service catalog') plus the exact source URL and the fields returned (id, price in USD, input parameters, deliverable). Its role as a discovery/pricing meta-tool for the x420_* family is unmistakable and clearly distinct from the operational siblings listed.

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?

It gives explicit when-to-use guidance: "Use it to see what the x420_* tools cost before calling one." That tells the agent the trigger condition clearly, but it states no exclusions (e.g. when the catalog is unnecessary because prices are already known) or failure behavior, so it falls just short of full when/when-not coverage.

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