Skip to main content
Glama

kelpo_get_project

Read-onlyIdempotent

Read a conversation: scene (brief), selected files, preparation state, jobs, messages and project_version (the version every scene call carries). Arguments: {"path": {"id": ""}}

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": {
      "path": "<path>"
    },
    "name": "kelpo_get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context by listing the sections of the returned payload (scene, files, prep state, jobs, messages, project_version), which matters since there is no output schema. It says nothing about payload size, pagination, or failure modes, keeping it at 4 rather than 5.

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

Conciseness4/5

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

Front-loaded with the verb and resource, then the payload enumeration, then the argument spec — a sensible order. The inline JSON argument block is slightly awkward but earns its place given 0% schema coverage. Two compact sentences, no filler.

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?

With no output schema, the description carries the burden of describing return values and does so by naming each returned section. With one nested required parameter and 0% schema coverage, it supplies the argument meaning inline. Annotations cover the safety profile. Nothing essential for a correct call 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 description coverage is 0%, so the schema documents neither 'path' nor 'id'. The description compensates by spelling out the argument shape inline and, critically, stating that the id is a '<project id>' — meaning the agent does not have to guess whether it is a scene id or job id. It does not explain why the id is wrapped in a 'path' object, which is the remaining ambiguity.

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?

Opens with a specific verb+resource ('Read a conversation') and then enumerates exactly what the read returns: scene brief, selected files, preparation state, jobs, messages, project_version. That enumeration distinguishes it from siblings like kelpo_get_shoot, kelpo_get_editing and kelpo_get_job without opening their schemas. It does not explicitly name those alternatives, so it stops short of a 5.

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 only implied: the parenthetical 'the version every scene call carries' hints that this tool is the prerequisite step before scene calls, but no when-to-use or when-not-to-use rule is stated. Nothing routes the agent away from kelpo_get_shoot or kelpo_get_editing. The implication is real but the agent must infer it.

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