Skip to main content
Glama

claw.mobile AI tools catalogue

Pricing for every tool

tool_pricing
Read-only

Every tool’s starting price and plans, cheapest first, each with priceSource, priceVerifiedAt and priceSourceUrl (the vendor pricing page it was read from). Same data as GET https://claw.mobile/api/tools/pricing.

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

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real value beyond that by disclosing the return fields (priceSource, priceVerifiedAt, priceSourceUrl) and their meaning — that the price was read from a vendor pricing page — which speaks to data freshness and trust. It stops short of describing pagination, cache/staleness behavior, or how missing prices are represented.

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?

A single front-loaded sentence establishes the resource, ordering, and per-item fields, with the parenthetical defining priceSourceUrl inline rather than in a separate clause. The endpoint-equivalence note is one short clause and adds orientation for API-literate agents without padding.

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 burden of explaining what is returned, and it does so for the key fields while noting ordering. The remaining gap — no mention of pagination, result limits, or how tools without pricing appear — is minor for a read-only, zero-parameter lookup.

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 the baseline is 4 and there is nothing for the description to compensate for. The description instead spends its words on the output shape, which is the only thing an agent could misunderstand here.

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 names the specific resource (every tool's starting price and plans) and adds scope details — ordering cheapest first and the provenance fields included — so an agent knows exactly what comes back. It doesn't explicitly contrast itself with siblings like compare_tools or list_tools, but the pricing focus is unmistakable from the text itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no routing to alternatives such as compare_tools for side-by-side analysis or list_tools for general enumeration. The 'cheapest first' ordering hints at a price-scan use case, but the agent must infer that on its own.

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