Skip to main content
Glama

Stratalize Intelligence

Get Company Intelligence Synthesis

get_company_intelligence_synthesis
Read-only

Live company intelligence synthesis: recent litigation, regulatory exposure, financial and news developments for a named company with ML-DSA-65 signed receipt for due diligence workflows. $1.00 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
focusNo
companyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false), so the description's added value is the cost ('$1.00 USDC per call') and the ML-DSA-65 signed receipt for verifiability — both genuinely useful behaviors an agent cannot get from structured fields. It stops short of disclosing latency, data recency window, or what the synthesis output looks like, so it is not a 5.

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

Conciseness4/5

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

A single front-loaded sentence that packs scope, verifiability, and price without filler. It is dense but readable; the pricing clause is arguably the only element that could be trimmed, and it earns its place given the paid nature of the call.

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?

With no output schema and no annotations covering cost or verification, the description does well to state what categories are synthesized, the signed receipt, and the price. But for a paid, open-world tool it omits the 'focus' parameter semantics, the time window of the underlying data, and any indication of output structure or length.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter burden and it largely does not. It clarifies 'company' only as 'a named company' — no hint whether that is a legal name, ticker, or domain — and the 'focus' parameter is never mentioned at all, leaving an agent to guess how to narrow the synthesis.

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 verb+resource ('Live company intelligence synthesis') and enumerates the content bundled in: litigation, regulatory exposure, financial and news developments. An agent knows what it gets. However, it does not distinguish itself from overlapping siblings like get_case_law_synthesis or get_regulatory_news_synthesis, which cover a subset of the same ground, so the differentiation a 5 requires is absent.

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 'for due diligence workflows' gives an implied use case, which is more than nothing. But there is no explicit when-to-use/when-not guidance, no routing to the narrower siblings that cover litigation or regulatory news alone, and no stated prerequisites for paying $1.00 USDC.

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