Skip to main content
Glama

kelpo_actor_catalog

Read-onlyIdempotent

List Kelpo's ready-to-use fictional actors (no real person): id, name, age, sex, profile, roles, photo URLs (look at them for a physical trait such as a beard), voice preview. Propose 2-3 by name; show each as a picture (markdown image of a photo URL) with name, age and one line of profile, never the id, a raw URL or a photo number (31/10: codes pasted to the person); use one with kelpo_expert_prepare actors [{"source": "catalog", "catalog_id": }]. No rights declaration is needed for them. Arguments: {"query": {"client_id": "", "lang": "fr"}}

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_actor_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / query / properties / lang / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "fr",
      -      "en"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "pattern": "^[A-Za-z]{2,3}([-_][A-Za-z]{2,4})?$",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / query / properties / lang / description
      Previous value: -"Language of the texts and voice preview (default: account language)."New value: +"The language of the person (any ISO code: fr, en, de, es…). Texts come in French or English; each actor says which languages its real voice speaks."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world behavior. The description adds useful non-schema context: actors are fictional and need no rights declaration, output includes photo URLs and voice preview, and display restrictions exist (never show id, raw URL, or photo number). It does not discuss result size or pagination, but that is a minor gap given the simple listing nature.

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?

The description is front-loaded with purpose and fields, and most sentences carry useful information, but it is a dense run-on paragraph with semicolons joining display rules, usage guidance and argument examples. Shorthand such as "(31/10: codes pasted to the person)" is cryptic and the structure could be cleaner.

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 simple read-only catalog with safety annotations already present, the description covers the output fields, display constraints, rights context, and integration with kelpo_expert_prepare. It lacks detail on result count or pagination, and does not fully explain the lang/client_id semantics, but it is broadly complete enough to invoke correctly.

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?

The description shows the argument shape as Arguments: {"query": {"client_id": "<client id>", "lang": "fr"}}, which helps construct the call. However, it does not explain what lang controls, that it may be null, or that client_id defaults to the first workspace; the nested schema fields carry those descriptions. Given the reported 0% schema coverage signal, the description does not fully compensate, though the single nested parameter is relatively simple.

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 a specific verb and resource: "List Kelpo's ready-to-use fictional actors (no real person)" and enumerates the returned fields. The parenthetical distinguishes it from real-person tools, but it does not explicitly name sibling alternatives such as kelpo_list_people, so sibling differentiation is only implicit.

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?

It gives a clear downstream workflow: propose 2-3 actors by name, show each as a picture with name, age and profile, and use the chosen one with kelpo_expert_prepare using actors [{"source": "catalog", "catalog_id": <id>}]. It also notes no rights declaration is needed. It stops short of explicit when-not or alternative scenarios, but the usage context is clear.

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