Skip to main content
Glama
Sign In
Clerkfield MCP Server

Clerkfield MCP Server

by bramontiventures
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Get coverage

get_coverage
Read-only

Shows which U.S. states business checks, lien searches, and lender searches cover; pass a two-letter state code to filter results or omit it for all states.

Instructions

Which U.S. states each check covers (business check, lien search, search by lender).

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

Input Schema

NameRequiredDescriptionDefault
stateNoTwo-letter state code; omit for every state

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 and locality are covered structurally. The description adds no behavioral context beyond content identification — no note that results are static reference data, whether coverage changes over time, or what the response looks like. For a trivial read that is tolerable, but it earns no credit above baseline.

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?

One short sentence with no filler, and the key scoping information is front-loaded. It is a grammatical fragment ('Which U.S. states each check covers...') rather than a full sentence, a minor structural weakness but not wasteful.

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?

There is no output schema, so the description must convey the return shape, and it only hints at it by listing the three check types as parentheticals. It never states that the result is a per-check mapping of supported states, which is the single most valuable fact for a caller with no output schema to consult.

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% and the single 'state' parameter is fully documented in the schema ('Two-letter state code; omit for every state'). The description adds nothing about the parameter, so the baseline 3 applies.

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 resource precisely — U.S. state coverage per check type — and enumerates the three check types (business check, lien search, search by lender), which tells an agent this is a coverage/metadata lookup. The verb is only implied (the tool name carries 'get'), and the sentence is a noun fragment, which keeps it short of a fully explicit verb+resource statement.

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 statement of when to use this tool, no prerequisites, and no reference to alternatives such as search_liens or verify_business (e.g., 'call this before those to confirm a state is supported'). An agent must infer the pre-flight/eligibility use case entirely on its own.

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

Deploy Server

Other Tools