Skip to main content
Glama

Contractor License Check Payment Quote

pros_verify_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/pros/verify (base $0.05; USDC on Base or Polygon); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET ?license=&purpose=consumer_contractor_check|license_verification. California contractor license check, corporations and LLCs only: status, classifications, issue and expiration dates, bond and workers' comp facts, business name, city/county, business phone. GET license and purpose=consumer_contractor_check|license_verification. No personal names; no ratings. Not for employment, credit, insurance, housing or tenancy decisions (FCRA). found:false = no displayable record; records may be withheld on request. Bad input: Not charged. USDC on Base or Polygon. On USDC on Base, errors are not charged, apart from the exceptions noted on a route. On USDC on Solana, and RLUSD on the XRP Ledger, a refused or failed request may still be charged. On Polygon (native USDC), a request is settled only when it

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, and the description still adds real value: base price, accepted chains, per-chain charging behavior for failed requests, 'Bad input: Not charged,' found:false semantics, withheld records, and FCRA use restrictions. That is well beyond what the structured fields provide, though the final settlement rule is cut off mid-sentence, leaving a dangling charge condition.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is a run-on that interleaves the quote's pricing, the downstream API's returned fields, legal/FCRA caveats, and payment rails, repeating 'USDC on Base or Polygon' and the GET license/purpose string. The settlement sentence is truncated entirely, so the structure fails at the end rather than just being wordy.

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-param quote tool with no output schema, the description does cover price, chain, endpoint, and payment flow. But it never says what the quote response looks like (amount, asset, address, expiry), and the dangling final clause about Polygon settlement leaves a charging rule unresolved.

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?

With zero parameters the baseline is 4, and the schema is empty so nothing is lost. The description does supply the query-parameter vocabulary used on the underlying HTTP call (license, purpose with its two enum-like values), which is useful context even though this tool accepts no arguments itself.

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 opening sentence is specific: it returns payment terms for a named endpoint at a stated base price, and explicitly says 'this tool never runs the check or pays,' which distinguishes a quote from an execution. The rest of the paragraph describes what the downstream license API returns (status, classifications, bond facts), which muddies what this tool itself produces, but the core purpose is still recoverable.

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?

It gives invocation mechanics (GET with ?license=...&purpose=consumer_contractor_check|license_verification) and payment protocol (x402 v2, 402 over HTTP), which implies when the tool is used. However, it never routes the agent among alternatives — no mention of sibling quote/x402 helpers or when to skip the quote and call the data endpoint directly, and no prerequisites stated up front.

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.