Skip to main content
Glama
yyy188
by yyy188

list_jama_project_relationships

Retrieve paginated relationships for a Jama project, with optional filtering by item ID to trace traceability links.

Instructions

List relationships for a project (cursor-paginated Jama endpoint).

Jama's ``/relationships`` endpoint requires a ``project`` filter and uses
``lastId`` cursor pagination. Optionally filter to relationships involving
a specific item (client-side on fromItem/toItem).

Args:
    project_id: numeric string Jama project id.
    item_id: optional numeric string item id to filter on.
    limit: max relationships to return (default 50).

Returns:
    {"project_id","count","results":[{id,relationship_type,source_item,
    target_item,suspect,name,modified_date}, ...]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
item_idNo
project_idYes
Behavior4/5

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

Covers pagination (lastId cursor), optional client-side filtering, and return format. Without annotations, it provides sufficient behavioral context for a list operation.

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?

Concise with front-loaded purpose. Each sentence adds value (purpose, endpoint details, args, returns). Minor redundancy but efficient.

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?

Complete for a list tool: explains pagination, filtering, and return format. With no output schema, it provides the necessary structure. All parameters documented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds meaning beyond the input schema: explains project_id as numeric string, item_id as optional, limit with default 50. Schema coverage was 0%, so description fully compensates.

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?

Description clearly states 'List relationships for a project' and explains the cursor-paginated endpoint. It distinguishes from sibling tools like 'get_jama_item_relationships' by indicating that item filtering is optional and client-side, implying the project-level scope.

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?

Description specifies when to use (project-level listing) and notes client-side filtering, cautioning about efficiency. However, it does not explicitly name alternative siblings or state when not to use this tool.

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