Skip to main content
Glama
yyy188
by yyy188

list_jama_releases

Retrieve releases and versions for a Jama project. Provide a project ID and optional limit to get release details including name, date, and status.

Instructions

List releases / versions for a project.

Args:
    project_id: numeric string Jama project id.
    limit: max releases to return (default 50).

Returns:
    {"project_id","count","results":[{id,name,release_date,status,
    description,modified_date}, ...]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
project_idYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes the return format and default limit, but lacks details on side effects, authentication needs, error handling, or whether the operation is read-only.

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 clear docstring format: brief sentence, Args section, Returns section. No redundant or missing information.

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?

For a simple list tool with no output schema, the description provides the return structure and parameter details. However, it omits error conditions, pagination behavior beyond limit, and assumes the project exists. Good but not fully comprehensive.

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%, but the description adds meaning: project_id is described as 'numeric string Jama project id' and limit as 'max releases to return (default 50)'. This goes beyond the schema labels. Could be improved by specifying allowed values or project_id format.

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 releases / versions for a project', using a specific verb and resource. This distinguishes it from sibling tools like list_jama_projects which list projects instead of releases.

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?

The description implies usage by explaining the project_id and limit parameters, but does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or prerequisites.

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