Skip to main content
Glama

company_facts__snapshot

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

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

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. Changed7 schema fields changed
    • addedInput schema / properties / enddt
      Added value: +{
      +  "description": "End date YYYY-MM-DD",
      +  "type": "string"
      +}
    • addedInput schema / properties / forms
      Added value: +{
      +  "description": "Comma-separated form types, e.g. 10-K,8-K",
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Max results (default 10, max 40)",
      +  "type": "integer"
      +}
    • removedInput schema / properties / name
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / q
      Added value: +{
      +  "description": "SEC EDGAR full-text query; quote phrases, e.g. \"going concern\"",
      +  "type": "string"
      +}
    • addedInput schema / properties / startdt
      Added value: +{
      +  "description": "Start date YYYY-MM-DD",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "q"
      +]
  3. Added
  4. Removed
  5. Changed2 schema fields changed
    • removedInput schema / properties / company / description
      Removed value: -"Company name"
    • removedInput schema / properties / domain
      Removed value: -{
      -  "description": "Domain (optional)",
      -  "type": "string"
      -}
  6. Changed2 schema fields changed
    • addedInput schema / properties / company / description
      Added value: +"Company name"
    • addedInput schema / properties / domain
      Added value: +{
      +  "description": "Domain (optional)",
      +  "type": "string"
      +}
  7. Changed1 schema field changed
    • removedInput schema / properties / domain
      Removed value: -{
      -  "type": "string"
      -}
  8. Changed3 schema fields changed
    • removedInput schema / properties / company / description
      Removed value: -"Company name to look up; \"q\" is accepted as an alias."
    • addedInput schema / properties / domain
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "company"
      -]
  9. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does disclose important traits: cost ($0.01/call in USDC on Base eip155:8453) and that payment rides in params._meta["x402/payment"], a hidden parameter not present in the schema. However, it says nothing about what the response contains, error/failure behavior when payment fails, or latency. The truncated 'Free…[20 more chars, already applied] Price: $0.01' fragment also leaves the pricing story ambiguous, which is a real gap for an agent that must decide whether it can afford to call.

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 capability list is front-loaded and dense with useful nouns, but the pricing information is repeated twice in immediate succession and one instance is a machine-truncated artifact ('Free…[20 more chars, already applied] Price: $0.01 per call in USDC on Base...'). That redundancy and debris cost the definition credibility and space without adding information.

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 aggregator with no annotations and no output schema, the definition covers the two things an agent most needs to know before calling: what data sources it returns and that it costs money via a specific payment mechanism. What is missing is the shape and breadth of the return payload (no output schema exists to compensate) and clarity on whether a free tier exists, given the truncated 'Free…' fragment.

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?

There is a single required parameter with 100% schema description coverage ('Company name or ticker, e.g. Apple Inc or AAPL'), so the schema already does the work and the baseline is 3. The description adds nothing about accepted formats, ticker-vs-name resolution, or ambiguity handling beyond the schema's own example.

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 a specific verb-like aggregation (facts in one call) and enumerates exactly which resources are covered: SEC EDGAR identity/filings and full-text filing search, OFAC SDN + EU sanctions, RDAP domain facts, DNS. That is far more specific than a sibling name alone. It stops short of explicitly contrasting itself with the granular siblings (company_facts__filings, company_facts__domain, company_facts__risk), so it is clear but not fully differentiated.

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 consolidated option and that the narrower siblings cover individual sources, but that inference is left to the agent. There is no explicit 'use this when you need everything at once; use company_facts__filings otherwise' statement and no stated preconditions 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