Skip to main content
Glama
Sign In

Corridome

by com.corridome
OverviewDiscussionsAdmin

List companies

list_companies
Read-onlyIdempotent

Portfolio companies in the register, A to Z, fifty at a time, each with its owner.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoFor the next page: the previous page's next_after (or the last name it listed).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / after / description
      Previous value: -"Start after this name (A to Z), for the next page."New value: +"For the next page: the previous page's next_after (or the last name it listed)."
    • changedInput schema / properties / after / maxLength
      Previous value: -200New value: +300
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

While annotations confirm the operation is read-only, the description adds crucial behavioral details like the list organization ('A to Z') and the pagination constraint ('fifty at a time'). These constraints help the agent manage expectations regarding data retrieval granularity.

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?

The description is a single, highly efficient sentence where every phrase serves to define the scope, sorting, or constraints of the data being retrieved.

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?

For a listing tool, providing the data source (register), the organizational logic (A to Z), and the batch limit (50) makes the definition very complete for an agent to understand its operational limits.

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?

Since schema coverage is 100%, the baseline is higher. The description adds value by defining operational parameters not in the schema, such as the 'A to Z' sorting order and the chunk size ('fifty at a time').

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

Purpose5/5

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

The description clearly defines the resource as 'Portfolio companies in the register' and the action as listing them 'A to Z,' making its purpose highly specific and easily distinguishable from other list/search siblings.

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?

The description implies usage by setting the scope to 'Portfolio companies in the register,' but it fails to offer explicit guidance on when this specific tool should be used versus broader search or category-specific list functions among the siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Corridome toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources