Skip to main content
Glama

Colorado Startups

A Leaderboard company

company
Read-onlyIdempotent

One Leaderboard honoree's public record: what it does, sector, city, region, boards, website and sources. Find the id with search.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe company id, such as 'acme-robotics'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety and idempotency profile is covered without the description. The description adds that this is a *public* record with cited sources, which is a meaningful behavioral detail. It doesn't say what happens when the id doesn't resolve (error vs. empty object).

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 front-loaded sentence lists exactly what is returned, followed by one short pointer to the discovery tool. There is no redundant restatement of the name or title and nothing to trim.

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 field enumeration carries the burden of telling the agent what comes back, and it does so at a field-name level. For a one-parameter read tool with full annotations, that is nearly sufficient; only return shape details and failure behavior are absent.

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 coverage is 100% and the schema already supplies the pattern, maxLength, and an example ('acme-robotics'), so the baseline is 3. The description's contribution is only the provenance hint that ids come from 'search', which is useful but doesn't clarify the id's format or validity rules.

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 exact resource (one Leaderboard honoree's public record) and enumerates the fields returned: what it does, sector, city, region, boards, website and sources. It also implicitly distinguishes itself from the bulk 'search' tool. The verb is implied rather than stated, which keeps it just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Find the id with search' gives an explicit prerequisite and points to the alternative tool for discovery, which is the exact context an agent needs. It stops short of stating what to do if the id is unknown or invalid, so it isn't exhaustive guidance.

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.