Skip to main content
Glama

Company Snapshot

company_snapshot
Read-only

Free sync company snapshot grounded in SEC EDGAR (0 credits). Returns headline/summary/filings + ladder to classify → Angel/CI. Informational triage only — not diligence.

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

Input Schema

NameRequiredDescriptionDefault
domainNoOptional company domain (e.g. stripe.com).
targetNoCompany or entity name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only and closed-world behavior, and the description adds useful context: zero-credit cost, synchronous execution, SEC EDGAR grounding, output contents, and the triage-only limitation. It does not cover rate limits or auth needs, but adds substantial value beyond annotations.

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

Conciseness5/5

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

Three short, front-loaded sentences: cost/source first, then return contents, then scope limitation. No redundant restatement of the tool name or schema.

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 simple two-optional-parameter read-only tool with no output schema, the description covers cost, source, return contents, and scope limits. The only notable ambiguity is the meaning of 'ladder to classify → Angel/CI', but otherwise it is complete enough to call correctly.

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 coverage is 100%, so the domain and target parameters are already documented in the schema. The description does not add format, precedence, or selection guidance beyond what the schema provides, so 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?

States a specific resource (company snapshot), data source (SEC EDGAR), cost (0 credits), and return contents (headline/summary/filings + classification ladder). It also distinguishes itself from diligence work, though the compressed 'ladder to classify → Angel/CI' phrasing does not fully spell out sibling routing.

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?

Implies use for free informational triage and explicitly excludes diligence ('not diligence'), but does not clearly state when to choose this over company_intelligence, angel_intelligence, or due_diligence. Guidance is present but relies on inference.

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