Skip to main content
Glama
yyy188
by yyy188

query_jama_endpoint

Perform read-only GET requests to any Jama REST API endpoint. Retrieve data from a single page or all pages using pagination.

Instructions

Power-user escape hatch: GET any Jama REST endpoint (read-only).

``path`` is appended to ``{JAMA_URL}{API_PREFIX}`` (e.g. ``"/projects"``).
Only GET is ever issued; the client is read-only by design.

Args:
    path: REST path beginning with '/', e.g. "/items/12345".
    params: optional 'k1=v1&k2=v2' query string.
    all_pages: if True, walk all pages and return a flat list of ``data``;
               if False (default), return only the first page.

Returns:
    {"path","data": <first-page data or flat list>}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
paramsNo
all_pagesNo
Behavior4/5

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

No annotations provided, so description carries full burden. Details the behavior: appends path to base URL, can walk all pages with all_pages flag, returns flat list. Lacks mention of rate limits or errors, but for a generic power-user tool this is acceptable.

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?

Well-structured with separate sections for general description, args, and returns. Slightly verbose but still efficient. Could be more concise, but structure aids readability.

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?

Covers key aspects: path format, query string syntax, pagination, return value. No output schema but return described. Complete enough for a generic API tool, though could mention potential errors (e.g., 404).

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?

Schema description coverage is 0%, but description compensates fully: explains path format, optional params query string, all_pages behavior. Also describes return format. All parameters are clearly semantically defined.

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 it's a power-user escape hatch for GET requests on any Jama REST endpoint (read-only). This distinguishes it from sibling tools that target specific endpoints.

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?

Explicitly notes that only GET is issued and the client is read-only, providing guidance on when to use. Could be more explicit about when not to use (e.g., for writes), but the 'read-only' warning is sufficient.

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