Skip to main content
Glama
yyy188
by yyy188

get_jama_item_children

Retrieve child items of a parent Jama item. Provide the item ID and optional limit to get decomposition children with details.

Instructions

List decomposition children of an item.

Args:
    item_id: numeric string Jama item id.
    limit: max children to return (default 50).

Returns:
    {"item_id","count","results":[{item_id,document_key,item_type_name,
    name,status,modified_date}, ...]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
item_idYes
Behavior4/5

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

The description reveals the return format and the limit parameter behavior (default 50). Since no annotations are provided, this is sufficient to understand the tool's read-only nature and output structure.

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

Conciseness5/5

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

The description is concise with a front-loaded purpose, followed by structured Args and Returns sections. No wasted words.

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?

The description covers input parameters and return format adequately for a simple tool. However, it does not clarify if 'children' refers to direct children or all descendants, which could be ambiguous.

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?

The Args section adds meaning beyond the schema: it specifies that item_id is a 'numeric string' and limit has a default of 50. This compensates for the 0% schema description coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'List decomposition children of an item', specifying the verb and resource. It distinguishes from sibling tools like 'get_jama_item' which retrieves a single item, and other get_* tools.

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 guidance on when to use this tool versus alternatives. For example, no mention of scenarios where 'get_jama_item_relationships' or 'search_jama_semantics' would be preferred.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yyy188/jama-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server