Skip to main content
Glama

Ni Biashara Shelves — Africa FX, freight & compliance checks (x402)

Texas legal fee check — one fee

check_legal_fee
Read-only

Texas legal fee check — one fee. One Texas judgment-work fee from the Ni Biashara Legal Shelf: the amount, the publishing office's source, and its confirmation status — confirmed on the office's own schedule, reported, a documented example county, or unconfirmed. An unconfirmed fee is answered with what is known, never an invented number. General information about public court processes, not legal advice. $0.05 USDC on Base. Returns the x402 URL to GET (402 → PAYMENT-SIGNATURE → delivery). Free to call this tool; payment happens on the URL.

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

Input Schema

NameRequiredDescriptionDefault
qNothe fee to check, e.g. recording an abstract (this or record_id required)
countyNocounty name: Collin, Dallas, Tarrant or Denton (optional)
record_idNorecord id from legal-process-lookup, e.g. abstract-recording-collin (this or q required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, and the description adds real context beyond them: the $0.05 USDC on Base price, the x402 payment handoff, and the important behavioral promise that an unconfirmed fee is answered with what is known rather than an invented number. It does not describe error or failure behavior in detail, keeping this below a 5.

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?

Purpose is front-loaded and each sentence carries a distinct payload: scope, return contents, confirmation tiers, disclaimer, price, and payment flow. The opening repeats the tool name/title ('Texas legal fee check — one fee'), which is minor waste, and the payment sentence is slightly overloaded.

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 usefully explains the return ('the x402 URL to GET') and the confirmation-status taxonomy an agent will encounter. It is nearly complete for a read-only lookup; remaining gaps are edge-case behavior on missing/ambiguous fee queries.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents q, county, and record_id including the either/or constraint. The description adds no syntax, enumeration, or format detail beyond that, so the baseline 3 is appropriate.

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?

States a specific verb and resource ('One Texas judgment-work fee from the Ni Biashara Legal Shelf') and enumerates what is returned: amount, publishing office's source, and confirmation status. It doesn't explicitly name a sibling it is not, so an agent must infer that the county fee card is the multi-fee alternative, but the 'one fee' scoping is clear.

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?

Useful procedural guidance is present: 'Free to call this tool; payment happens on the URL' with the 402 → PAYMENT-SIGNATURE → delivery flow. However, there is no explicit when-to-use/when-not-use guidance relative to lookup_legal_process or get_legal_county_fee_card, so the choice among siblings is implied 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