Skip to main content
Glama

company_facts__lookup_delta

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/delta

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_delta"
  }
}

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

A3.7/5.0
Behavior4/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 deliver important context: a paid call at $0.01 in USDC on Base (eip155:8453) via x402 in params._meta, plus the concrete HTTP endpoint. What it omits is the response shape (no output schema exists), whether all data sources are always queried, and error/rate-limit behavior.

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 value proposition is front-loaded, but the pricing sentence is stated twice — once in the opening and again as 'Price: $0.01 per call in USDC on Base (eip155:8453)...' — and a truncated artifact ('Free…[20 more chars, already applied]') is embedded mid-description. The endpoint line is useful; the duplication is waste.

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 an aggregating lookup with one parameter and no output schema, the description covers the key things an agent needs: what data classes come back, what it costs, and how to pay/transport it. It is only incomplete in not indicating result structure or how the combined response differs from the single-source siblings.

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 with 100% schema description coverage that already gives examples ('Apple Inc' or 'AAPL'), so the schema does the semantic work. The description adds nothing about accepted forms (ticker vs. legal name variants, ambiguity resolution), which is fine at baseline for a one-parameter tool.

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 specific resources aggregated — SEC EDGAR identity/filings and full-text search, OFAC SDN + EU sanctions, RDAP domain facts, DNS — so an agent can tell it is a composite company/domain lookup. It does not, however, distinguish itself from closely related siblings like company_facts__lookup, company_facts__dossier or company_facts__risk, so the boundary is left implicit.

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' weakly implies this is the one-shot aggregate to use instead of combining the individual source tools, which is a usable but indirect usage signal. There are no explicit when-to-use/when-not conditions, no mention of alternatives, and no guidance on choosing this over company_facts__lookup or dossier.

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