Skip to main content
Glama
yyy188
by yyy188

get_jama_item_attachments

List attachment metadata for a Jama item, including file name, type, size, and dates, without downloading the file.

Instructions

List attachment metadata for an item (no binary download).

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

Returns:
    {"item_id","count","results":[{id,name,file_type,file_size,
    mime_type,created_date,modified_date}, ...]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
item_idYes
Behavior3/5

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

No annotations are provided. The description indicates the operation is read-only ('no binary download') and describes the return format. However, it does not disclose authentication needs, rate limits, or potential side effects.

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 very concise with a clear purpose statement, followed by a structured Args and Returns sections. Every sentence adds value without redundancy.

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?

Given no output schema, the description documents the return structure. It covers the tool's purpose, parameters, and output format. Minor missing details like pagination or error handling, but adequate for a simple list tool.

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 description carries the full burden. It explains 'item_id' as a numeric string and 'limit' as max attachments with default 50, adding meaning beyond the schema types.

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 explicitly states the tool lists attachment metadata for an item, and clarifies it does not include binary download. This clearly distinguishes it from other tools in the sibling list like get_jama_item or search tools.

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 provides basic usage through Args, but lacks explicit guidance on when to use this tool versus alternatives. No 'when not to use' or comparison to siblings is mentioned.

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