Skip to main content
Glama

company_facts__lookup_agent_check

Company, sanctions and domain facts in one call: SEC EDGAR identity/filings and full-text filing search, OFAC SDN + EU sanctions screening, RDAP domain facts, DNS. $0.01 per call in USDC on Base. Free…[20 more chars, already applied] Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/company-facts/lookup/agent-check

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": {
      "company": "<company>"
    },
    "name": "company_facts__lookup_agent_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesCompany name or ticker, e.g. 'Apple Inc' or 'AAPL'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / company
      Added value: +{
      +  "description": "Company name or ticker, e.g. 'Apple Inc' or 'AAPL'",
      +  "type": "string"
      +}
    • removedInput schema / properties / enddt
      Removed value: -{
      -  "description": "End date YYYY-MM-DD",
      -  "type": "string"
      -}
    • removedInput schema / properties / forms
      Removed value: -{
      -  "description": "Comma-separated form types, e.g. 10-K,8-K",
      -  "type": "string"
      -}
    • removedInput schema / properties / limit
      Removed value: -{
      -  "description": "Max results (default 10, max 40)",
      -  "type": "integer"
      -}
    • removedInput schema / properties / q
      Removed value: -{
      -  "description": "SEC EDGAR full-text query; quote phrases, e.g. \"going concern\"",
      -  "type": "string"
      -}
    • removedInput schema / properties / startdt
      Removed value: -{
      -  "description": "Start date YYYY-MM-DD",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "q"
      -]New value: +[
      +  "company"
      +]
  2. Added
  3. Removed
  4. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden and does well on two fronts: it discloses the $0.01 per-call cost and the x402 payment mechanism via params._meta['x402/payment'], and the HTTP endpoint makes the read-only nature apparent. It does not state required permissions, latency, or partial-failure behavior across the four upstream sources, and notably the payment parameter it mandates is absent from the input schema.

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

Conciseness3/5

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

The data-source enumeration is front-loaded and useful, but the pricing sentence is duplicated and truncated ('$0.01 per call in USDC on Base. Free…' followed by 'Price: $0.01 per call in USDC on Base (eip155:8453)'), and the raw HTTP verb/URL is tacked on. Two sentences repeat the same payment fact, diluting the otherwise tight opening.

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?

Given a paid, multi-source lookup with no output schema and no annotations, the description covers cost and payment adequately but leaves the result shape entirely unspecified. An agent cannot tell whether it receives separate company/sanctions/domain sections, nulls for missing sources, or errors on partial failure.

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?

There is a single required parameter at 100% schema coverage, and the schema already gives an example ('Apple Inc' or 'AAPL'). The description adds no further semantics for 'company' (e.g. whether a domain can be passed for the RDAP/DNS portions), which is a small gap but above the high-coverage baseline.

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?

Names the concrete resources and verbs covered: 'SEC EDGAR identity/filings and full-text filing search, OFAC SDN + EU sanctions screening, RDAP domain facts, DNS'. An agent knows exactly what data comes back. It never distinguishes this combined 'agent-check' from siblings like company_facts__lookup or check_sanctions__screen, so differentiation is inferred only from the enumerated sources.

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?

The phrase 'in one call' implies this is the convenience/composite option for agents that want everything at once, which is implicit when-to-use guidance. There is no explicit statement of when to prefer this over the narrower sibling tools, nor any exclusion or prerequisite beyond payment.

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