Skip to main content
Glama

clearhouse

by sh.clearhouse

quote_call

Step 1 of a paid call (non-custodial). Fetches the service's payment requirements and returns the exact EIP-712 typed data your agent must sign with ITS OWN key. Nothing is charged until you sign and pass the result to call_service. If the service is free, says so.

Args:
    listing_id: id from search_agents
    payer_address: your agent's wallet address (the key that will sign)
    args_json: JSON object of query args for the service

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
args_jsonNo{}
listing_idYes
payer_addressYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and handles it well. It discloses non-custodial behavior, that no charge occurs until signing, that the agent signs with its own key, and that free services are reported as such. It omits potential failure modes or rate limits, but the core behavioral traits are transparent.

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?

The description is front-loaded with the most critical fact, 'Step 1 of a paid call', followed by a tight behavioral overview and a clean Args list. Every sentence earns its place with no filler.

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?

An output schema exists, so explaining return values is unnecessary. The description covers the payment workflow, signing requirement, charge behavior, and free-service case, giving an agent everything it needs to invoke the tool correctly.

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?

Schema description coverage is 0%, so the description must add meaning to parameters. It does: listing_id is tied to search_agents, payer_address is explicitly the agent's signing wallet, and args_json is described as a JSON object of query args. This goes beyond the bare schema, although args_json could be more detailed about expected structure.

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 description uses a specific verb, 'fetches', and clearly identifies the resource: the service's payment requirements and the exact EIP-712 typed data to sign. It also distinguishes itself from call_service by explicitly labeling itself 'Step 1 of a paid call' and noting the result must be passed to call_service.

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?

The description provides strong workflow context: it is Step 1 before call_service, and nothing is charged until the agent signs and passes the result. It does not explicitly mention when not to use the tool or name alternative sibling tools like search_agents, but the ordering and 'pass to call_service' instruction make the intended usage clear.

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

All clearhouse toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool covers a distinct stage of the workflow: discovery (search_agents), marketplace-level data (index_stats), per-service evidence (service_evidence), pricing/authorization (quote_call), and execution (call_service). There is no meaningful overlap or ambiguity between tool purposes.

Naming Consistency3/5

Three tools use a clear verb_noun pattern (call_service, quote_call, search_agents), but index_stats and service_evidence are noun phrases. The names are readable and snake_case is consistent, but the convention is mixed rather than uniform.

Tool Count5/5

Five tools is well-scoped for a service gateway: search, evidence, stats, quote, and call. Each tool has a clear role and no tool feels redundant or unnecessary.

Completeness5/5

The toolset covers the full agent-facing lifecycle: discovering services, inspecting evidence and index totals, obtaining payment quotes, and executing calls with signed receipts. There are no obvious dead ends or missing operations within the stated domain.

Resources