Skip to main content
Glama

kelpo_list_people

Read-onlyIdempotent

List the people of the library (id, name, photos, voice): the person themself or actors already used. Use their id as person_id (kelpo_expert_prepare actors source library). Arguments: {"query": {"client_id": "<client_id>"}}

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

Input Schema

NameRequiredDescriptionDefault
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is settled. The description adds value by disclosing the returned fields (id, name, photos, voice), which matters since there is no output schema, but it says nothing about pagination, result size, or what client_id actually scopes, leaving the behavioral picture thin.

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?

Purpose is front-loaded and the field list is efficient, but the trailing raw JSON argument block duplicates structured schema data and adds clutter rather than meaning. The parenthetical workflow hint is dense and slightly awkward to parse.

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

Completeness3/5

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

For a simple read-only list tool with no output schema, describing the returned fields and the downstream person_id use covers most of what an agent needs. The notable gap is the completely undocumented client_id argument, which is the only parameter and thus the one thing a caller needs explained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single client_id parameter is a nested field with no explanation anywhere. The embedded argument example only restates the schema shape rather than explaining what client_id means or whether omitting the default empty string changes the result, so the description fails to compensate for the coverage gap.

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 opens with a specific verb and resource ("List the people of the library") and enumerates the fields returned (id, name, photos, voice), plus a clarifying note that entries can be the person themselves or an actor already used. It does not, however, distinguish this from the sibling kelpo_actor_catalog, which an agent could plausibly confuse it with.

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?

It gives a downstream usage hint — feed the returned id as person_id into kelpo_expert_prepare as an actors source — which is genuinely helpful workflow guidance. But it never states when NOT to use this tool or how it differs from kelpo_actor_catalog, so the choice between the two remains inferred.

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