Skip to main content
Glama

kelpo_input_requirements

Read-onlyIdempotent

Read required, conditional and optional inputs and exact questions to ask. Uses the same selected references and library as the studio. No generation or charge. 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_input_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context that it uses the same selected references and library as the studio and incurs no generation or charge, but says nothing about auth, rate limits, or return behavior.

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?

The description is short and front-loads the core action before adding context and the argument. The inline argument JSON is slightly redundant with the schema but useful, and the 'same selected references and library' sentence is a bit vague.

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 tool this covers the main behavior and the one required argument, and the lack of output schema means return details are absent. It is adequate but does not describe the return shape or clarify when to choose this tool over related siblings.

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 0%, so the description must compensate; it does so by giving the exact argument shape and clarifying that path.id is a project id. The nested path object itself is not further explained, but the single meaningful field is clear.

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 states a specific verb and resource: read required, conditional, and optional inputs plus exact questions to ask. It also distinguishes itself from generation tools by noting 'No generation or charge', though it does not differentiate itself from other read-oriented kelpo siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit when-to-use guidance, alternatives, or exclusions. Usage is only implied by the phrase 'exact questions to ask' and the no-charge note, which is insufficient for routing among many sibling tools.

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