Skip to main content
Glama

Distribute Software

Company coverage

get_company
Read-onlyIdempotent

One company's last 30 days: how many stories mentioned it, its best covered recent stories, and, for AI labs, its own posts. Links to its page on distribute.software.

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": {
      "slug": "<slug>",
      "context": "<context>"
    },
    "name": "get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesA company slug from list_companies, e.g. 'apple' or 'nvidia'.
contextYesA few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other personal details.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

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 establish readOnly, idempotent, non-destructive, closed-world behavior, so the description is only asked to add context. It does so by disclosing what is returned (mention counts, top stories, AI-lab self-posts, an external link), which goes beyond the annotations. It does not explain how 'best covered' is ranked or what happens for an unknown slug.

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?

A single dense sentence with the entity and time window front-loaded, followed by the three content components. No filler or restatement of the name.

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?

With no output schema, the description carries the burden of explaining returns and does so adequately for a read-only lookup. The fully documented schema covers the analytics parameters. Only the ranking logic and error behavior for unknown slugs are left unstated, which is minor for this complexity.

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 description coverage is 100%, so every parameter, including the analytics-only context, llm_model, and conversation_id, is already documented. The description adds no parameter-level detail such as slug format or behavior on invalid slugs, 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?

The description states a concrete resource (one company) with an explicit scope (last 30 days) and enumerates the payload: mention counts, best-covered recent stories, and AI-lab posts. It is clear enough to distinguish from list_companies or search_stories, though it never names a sibling to contrast with.

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?

Usage is implied rather than stated: the 30-day window and 'best covered' framing suggest a per-company overview, and the schema's reference to list_companies implies slug discovery happens first. There is no explicit 'use this instead of search_stories when...' guidance or statement of when not to call it.

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