Skip to main content
Glama

Search numbers

search_numbers
Read-only

Find numbers in the Tally record by words, for example 'anthropic valuation', 'openai revenue', 'langchain stars', 'cursor plan price'. Returns each match with its id, current value and page, and any company whose name matches.

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

Input Schema

NameRequiredDescriptionDefault
queryYesA company or project name, optionally with what to measure.

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 declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: matches include id, current value, page, and company-name matches even when the metric is unstated. It does not mention result limits, ranking, or empty-result behavior.

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 front-loaded sentences: the search semantics come first, then the return shape. The four examples are slightly redundant but each illustrates a different company/metric pairing, so little is wasted.

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 annotations covering the safety profile, the description does enough by describing the fields returned. Only the absence of result-count/empty-match behavior keeps it from being fully self-sufficient.

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's examples ('anthropic valuation', 'cursor plan price') actively demonstrate the company-plus-metric query form the schema only hints at, effectively teaching accepted input shapes.

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 and resource: find numbers in the Tally record by words. The four example queries make the free-text search behavior concrete and clearly differentiate it from a lookup-by-id tool, though no sibling is named explicitly.

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 by the examples — you search when you have a company or metric phrase rather than an identifier — but there is no explicit statement of when to use this versus get_number or get_company, and no note about what to do when no match is returned.

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.