List all 12 paid tools with live prices + free preview routes (FREE, no payment)
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| docs | Yes | ||
| server | Yes | ||
| network | Yes | ||
| version | Yes | ||
| currency | Yes | ||
| free_tools | Yes | ||
| how_to_pay | No | ||
| paid_tools | Yes | ||
| facilitator | No | ||
| free_previews_http | No |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "currency": {
+ "type": "string"
+ },
+ "docs": {
+ "type": "string"
+ },
+ "facilitator": {
+ "type": "string"
+ },
+ "free_previews_http": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "free_tools": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "how_to_pay": {
+ "type": "string"
+ },
+ "network": {
+ "type": "string"
+ },
+ "paid_tools": {
+ "items": {
+ "properties": {
+ "description": {
+ "type": "string"
+ },
+ "price_usd": {
+ "type": "number"
+ },
+ "tool": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "tool",
+ "price_usd",
+ "description"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "server": {
+ "type": "string"
+ },
+ "version": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "server",
+ "version",
+ "network",
+ "currency",
+ "paid_tools",
+ "free_tools",
+ "docs"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral transparency. It notes 'FREE, no payment', implying no cost, but does not explicitly state whether the operation is read-only or has any side effects. As a catalog listing, it is likely safe, but this is not explicitly disclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that front-loads the primary purpose. It avoids unnecessary detail and is well-structured for an agent to quickly parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity and the presence of an output schema, the description does not need to detail return formats. It provides sufficient context about what the catalog includes (paid tools, live prices, free preview routes). Minor ambiguity remains about the exact structure of the output, but the output schema covers that.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has no parameters, and the schema coverage is effectively 100% (since there is nothing to document). Per the rubric baseline, a score of 3 is appropriate when no parameter information is needed beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: listing all 12 paid tools with live prices and free preview routes. It uses the specific verb 'list' and refers to an identifiable resource (the catalog of tools). It is immediately distinguishable from sibling tools, which are individual utilities.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description conveys the basic usage (viewing the catalog) but does not explicitly state when to use this tool versus alternatives. However, since the tool has no parameters and the purpose is straightforward, the implicit guidance is adequate, though not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.