Skip to main content
Glama

Klinio

Get the companies

get_results
Read-only

The companies a search found, with website, emails and phones, oldest first. Only the ones with an email or phone unless only_contacts is false. Send next_cursor back as cursor for the next page.

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

Input Schema

NameRequiredDescriptionDefault
limitNoCompanies per page (default 50).
cursorNoThe next_cursor of the previous page.
search_idYesThe search's id.
only_contactsNoOnly companies with an email or phone (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The readOnlyHint annotation already marks this as a safe read operation. The description adds useful behavior beyond that: results are ordered oldest first, contact-only filtering is enabled by default, and pagination uses next_cursor as cursor.

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?

Three short sentences, front-loaded with the result set and immediately followed by the two behavioral details an agent needs: contact filtering and pagination. There is no irrelevant wording.

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

Completeness5/5

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

For a read-only paginated results tool with no output schema, the description covers the returned fields, ordering, default filtering, and pagination mechanism. Nothing essential for correct invocation is missing.

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 the schema already documents all four parameters. The description still adds practical meaning by explaining how cursor and next_cursor relate across pages and by clarifying the default effect of only_contacts.

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 clearly states that this returns companies found by a search, including website, emails and phones. The verb is implicit rather than explicit, and it does not differentiate itself from sibling tools such as get_search or list_searches.

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: call it after a search, use only_contacts=false to include companies without contact details, and pass next_cursor back as cursor. However, it gives no explicit guidance on when to use this tool versus alternatives.

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