Skip to main content
Glama

UAI x402 Security Tools

catalog

List UAI x402-paid security tools, REST endpoints, and prices (free)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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. "List" implies a read-only operation and "(free)" usefully discloses that this call itself incurs no x402 charge, which is a genuine behavioral trait. However, it says nothing about authentication, whether the listed endpoints require payment credentials, response format, or pagination.

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?

One sentence with no filler, and the core resource (tools, endpoints, prices) is front-loaded. It is slightly dense with unexplained terminology, but nothing is redundant.

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 zero-parameter listing tool this is close to sufficient, and the description names what is returned (tools, endpoints, prices). Since there is no output schema, a brief note on the shape of each catalog entry or on prerequisites for the paid endpoints would close the remaining gap.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies the call is argument-free by presenting a plain catalog listing.

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 opens with a specific verb+resource: "List UAI x402-paid security tools, REST endpoints, and prices". That is enough to distinguish a discovery/directory tool from the sibling scan/audit tools. The only drag is the unexplained "UAI x402-paid" jargon, which an agent may not decode without prior context.

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 to discover available paid tools and their pricing. There is no explicit when-to-use statement, no mention of calling it before invoking a paid endpoint, and no exclusions or alternatives named. Adequate but leaves routing to inference.

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