Skip to main content
Glama

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. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety and external-reach semantics are covered. The description adds genuinely useful non-annotation facts: $1.00 USDC per call and an ML-DSA-65 signed receipt for provenance. It does not disclose latency, freshness guarantees beyond "live", or what happens on failure.

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?

Two compact sentences, front-loaded with the capability and followed by the commercial/trust terms. No filler, though the second sentence packs pricing and signing into one clause that could read more cleanly.

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 only two parameters, no output schema, and read-only annotations, the definition is mostly complete: it says what is synthesized, the cost, and the receipt. The unresolved gaps are the meaning of `focus` and any indication of output shape or coverage depth for a paid, open-world call.

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 coverage is 0%, so the description carries the full burden. "For a named company" loosely implies the required `company` parameter, but the optional `focus` parameter is never mentioned or explained — an agent cannot tell whether it takes a topic, a jurisdiction, or a domain keyword, nor how it interacts with the enumerated content areas.

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+resource pair (company intelligence synthesis) and enumerates the content domains it covers: recent litigation, regulatory exposure, financial and news developments. This is far more concrete than a sibling like get_company_salary_disclosure or get_docket_intelligence, though it never explicitly contrasts itself with those narrower siblings.

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?

"for due diligence workflows" gives a usage context, which is more than nothing, but there is no statement of when to pick this synthesis over the many narrower siblings (docket, regulatory news, case law, financials). The agent must infer that this is the aggregating option.

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