Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

find_manual_siblings

Read-only

Lists sibling revisions of the same parametric design that use different parameter values, optionally including the current or retired versions for comparison and audit.

Instructions

List sibling revisions of a parametric design (Business+).

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": {
      "manual_id": "<manual_id>"
    },
    "name": "find_manual_siblings"
  }
}

Input Schema

NameRequiredDescriptionDefault
manual_idYesThe reference revision. All other revisions of the same design with different parameter values come back as siblings.
include_selfNoWhen True, the input revision is returned alongside its siblings (useful for a UI that wants the full set with the current row marked). Default: false.
include_retiredNoWhen True, surface retired siblings in the result (audit / portfolio review). Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • changedInput schema / properties / include_retired / description
      Previous value: -"Default: false."New value: +"When True, surface retired siblings in the result (audit / portfolio review). Default: false."
    • changedInput schema / properties / include_self / description
      Previous value: -"Default: false."New value: +"When True, the input revision is returned alongside its siblings (useful for a UI that wants the full set with the current row marked). Default: false."
    • addedInput schema / properties / manual_id / description
      Added value: +"The reference revision.  All other revisions of the same design with different parameter values come back as siblings."
  2. Addedv1.5.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only the Business+ tier requirement; it does not explain how siblings are determined or how many might return, though the parameter descriptions carry some of that context.

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?

A single short sentence with no filler, but it is thin rather than front-loaded with the routing information an agent needs. Nothing is wasted, though little is delivered.

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?

The tool is simple (one required string, two booleans, no output schema) and the schema documents parameters well, so the essentials are covered. Still, with no output schema the description should indicate what a sibling record contains, and the absence of sibling differentiation leaves a gap.

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?

Schema coverage is 100%, and the schema descriptions for manual_id, include_self, and include_retired are already thorough, including defaults and rationale. The description adds nothing beyond the schema, so the baseline of 3 applies.

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: it lists sibling revisions of a parametric design. It does not name or differentiate itself from near-siblings such as list_manual_history, get_manual_revision, or batch_verify_manuals, so an agent must infer the boundary from the name alone.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative tool is named. The parenthetical '(Business+)' hints at a tier prerequisite but does not explain that it gates access or what to do otherwise.

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

Deploy Server

Other Tools