Skip to main content
Glama

Company Finders

Get a list

get_list
Read-only

The state of a list and, when it is done, every business with what was found. Free.

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": "get_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id build_list returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds a genuinely useful behavioral fact — that results only appear once the list is finished, implying a state/polling model — but the trailing 'Free.' is cryptic (cost? credits? no charge?) and unexplained, and the possible state values are never enumerated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded with the return content, which is good, but it is under-specified rather than concise: the one-word fragment 'Free.' is ambiguous and the sentence's grammar makes the completion condition hard to parse on first read.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an asynchronous job-status tool, the description omits the things an agent most needs: what states exist, whether to poll and how often, and what the payload looks like when incomplete versus complete. With no output schema and only annotations covering the safety profile, the description leaves the core calling pattern underspecified.

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% and the single parameter 'id' is documented as 'The id build_list returned.', so the schema carries the semantics. The description adds nothing about the id (e.g., whether ids expire or are reusable), which is acceptable at baseline given full coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys that this returns a list's current state and, once complete, the businesses found, but it is phrased as a noun fragment ('The state of a list') with no explicit verb and no statement that it is a retrieval/polling operation. It hints at the async relationship to build_list but never names it, so the agent must infer that this is the companion read to a list-building job.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance: nothing says to call this after build_list, whether it should be polled repeatedly, or what to do when the state is not yet done. The phrase 'when it is done' implies a polling pattern but the agent must construct that workflow itself.

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