Skip to main content
Glama

Get a company's numbers

get_company
Read-only

Every number Tally keeps about one company, project, sector or investor, each with its current value and id.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe name, for example 'Anthropic', 'Stripe', 'LangChain', or a stock ticker.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value by saying each result carries its current value and id, but says nothing about result volume, ordering, pagination, or behavior when the name is unknown or ambiguous.

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 with no filler; the broadest information (all numbers for one entity) comes first and the payload shape follows. The phrasing is a noun phrase rather than an action statement, which costs a bit of immediacy.

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 one required parameter, no output schema, and read-only annotations, the description does the necessary work by describing the returned shape (value plus id per number). It is only incomplete around edge cases such as unknown or ambiguous names and whether results are capped.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema does not: the single 'name' argument can identify a project, sector, or investor, not only a company as the schema examples ('Anthropic', 'Stripe', a ticker) imply. This broadens the agent's understanding of acceptable inputs, though it also creates tension with the title 'Get a company's numbers'.

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 the resource precisely ('every number Tally keeps about one company, project, sector or investor') and signals it is a bulk retrieval, which separates it from get_number in the sibling list. It lacks an explicit verb ('retrieve'/'list') and never names an alternative tool, so it falls short of the discriminating 5.

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?

Use is only implied through scope: 'Every number' suggests this is the broad 'give me the full picture for one entity' call, in contrast to search_numbers or get_number. There is no explicit when-to-use, when-not-to-use, or named alternative, so the agent must infer routing.

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.