Skip to main content
Glama

Kit Rx catalog

kitrx_catalog
Read-only

Free (no payment). Lists every Kit Rx tool with its price in USD and USDC atomic units, parameters, example arguments and the equivalent HTTP x402 URL, plus the accepted payment networks and payTo address.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the call is free (no payment required) — meaningful in an x402/payment ecosystem where sibling tools cost money — and it discloses what pricing metadata (USD, USDC atomic units, payTo, networks) the response contains.

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, front-loaded with the most decision-relevant fact ('Free (no payment)') and then a dense enumeration of returned fields. Every listed item is informative, though the run-on list of return contents could be tightened into a short structured phrase.

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?

With no output schema, the description carries the full burden of explaining the return value, and it does so by enumerating the fields an agent would receive (prices, params, examples, x402 URL, networks, payTo). Only the response shape/format is left implicit, which is a minor gap for a zero-parameter catalog tool.

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 no per-parameter meaning to add and the baseline of 4 applies. The description correctly signals a parameter-free call by describing only returned content.

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 ('Lists every Kit Rx tool') and enumerates the payload: price in USD and USDC atomic units, parameters, example arguments, x402 HTTP URL, payment networks and payTo address. That is detailed enough to separate it from the sibling rx_* tools, which perform actual lookups rather than describe the catalog.

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?

The lead phrase 'Free (no payment)' implies this is the no-cost discovery entry point ahead of paid rx_* / x402 calls, but the description never explicitly says 'call this first to discover tools' or names any alternative. Usage is inferable rather than stated.

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