Skip to main content
Glama

Firmograph enrich

enrich
Read-onlyIdempotent

Firmograph Public Plane company enrichment by domain. Paid model: x402 v2 scheme exact quote-then-pay, USDC on Base (eip155:8453), atoms legal 30000 / web_inferred 10000 (DG-FG-PRICE-001); not-found / upstream = no charge (unpaid requests only). While the service lock is closed, tools/call answers HTTP 503 live_fetch_locked with no offer. When it is open, tools/call returns only the x402 PaymentRequired quote (isError: true) and never enrichment data. Settlement over MCP is not enabled - use HTTP POST /v1/enrich only. Fixed-host public sources: legal = notable-firm GLEIF ACTIVE via Wikidata domain->LEI; web_inferred = DNS (+ optional Wikidata-without-LEI / gTLD RDAP); .ch/.li have no RDAP. Not universal US SMB coverage. Support display: email:apigrid@mail.grokbot.com (CEO-role shared inbox display only; no SLA; no human-reply claim; not verified delivery; no outbound mail; not a refund service).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "enrich"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesCompany web domain, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and idempotentHint; the description adds substantive behavior beyond them: exact pricing (atoms 30000 / web_inferred 10000), the no-charge rule for not-found/upstream errors, the 503 lock state, the isError:true quote-only response, and the fact that MCP settlement is disabled. Nothing contradicts the read-only/idempotent annotations, since enrichment is a fetch.

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?

Purpose and payment mechanics are reasonably front-loaded, but the text is a single dense block that welds pricing, lock states, data-source provenance, coverage disclaimers, and a support email into one run-on. The final support-display clause (shared inbox, no SLA, no human-reply claim, not verified delivery, no outbound mail, not a refund service) is contract boilerplate that does nothing for tool selection or invocation.

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?

For a one-parameter paid fetch with no output schema and no siblings, the description covers the essentials an agent must know before calling: cost, charge exemptions, the possibility of a 503, and that a successful MCP call yields a payment quote rather than data. Coverage caveats ('Not universal US SMB coverage') are a useful extra. Only the noise-to-signal ratio keeps it from complete.

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 coverage is 100% for the single required 'domain' parameter, so the baseline would be 3. The description earns above baseline by explaining what the domain drives: legal lookups via notable-firm GLEIF ACTIVE through a Wikidata domain->LEI mapping, and web_inferred via DNS, optional Wikidata-without-LEI, and gTLD RDAP, with .ch/.li having no RDAP. That meaningfully constrains what values are worth passing.

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 gives a specific verb and resource: 'company enrichment by domain.' That is concrete enough for an agent to know the operation, though the jargon ('Public Plane', 'Firmograph') adds noise rather than precision. No siblings exist to differentiate against, so the lack of alternative routing costs nothing.

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 is unusually explicit about the operating conditions: while the service lock is closed the call returns 503 live_fetch_locked, and when open it returns only the x402 PaymentRequired quote and 'never enrichment data', with settlement over MCP not enabled and HTTP POST /v1/enrich named as the real path. That effectively tells an agent when not to expect payload data. It stops short of a clean 'use this / use that' routing statement, so it is not a 5.

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