Skip to main content
Glama
yyy188
by yyy188

query_jama_native_metadata

Retrieve exact metadata records from Jama projects by filtering with document key, status, item type, or keyword. Provides precise, native API results.

Instructions

Query Jama's native REST API directly for exact metadata filtering.

Use ONLY for precise lookups (exact document key, exact status, exact
item_type) — it returns empty on any misspelling. For topical, fuzzy or
natural-language questions, prefer `search_jama_semantics` instead.

Bypasses the vector store to answer precise questions (exact document key,
specific status, specific item type). Handles pagination internally and
returns up to 20 core metadata records.

Args:
    project_id: numeric string Jama project id.
    document_key: exact Jama document key (e.g. "SA-TC-7").
    item_type: Jama item-type id as a numeric string (e.g. "89011" for Test
               Case). Pass None for all types. Kept as a string (not int)
               to match `search_jama_semantics` and the other MCP tools,
               which all take ids as numeric strings.
    status: exact status string (e.g. "BLOCKED", "APPROVED").
    keyword: full-text 'contains' filter delegated to Jama.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNo
keywordNo
item_typeNo
project_idYes
document_keyNo
Behavior4/5

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

No annotations present, so description carries full weight. It discloses bypassing vector store, internal pagination, 20-record limit, and return structure. Lacks details on error handling, rate limits, or authentication, but adequate for a read-only query tool.

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 summary line, usage guidelines, behavior, parameter details, and return format. Slightly verbose but each sentence adds value. No redundant 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?

Covers purpose, usage, parameters, behavior, and return format. Mentions pagination and result limit. Minor gaps: no error handling or edge cases. Good for 5-parameter tool without output schema.

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 coverage is 0% with 5 parameters and no descriptions. Description explains each parameter: project_id, document_key, item_type (string consistency rationale), status (example values), keyword (full-text filter). Fully compensates for missing schema descriptions.

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 verb 'Query' and resource 'Jama's native REST API' with purpose 'exact metadata filtering'. It distinguishes from sibling 'search_jama_semantics' by specifying precise vs. fuzzy usage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use ONLY for precise lookups' and directs to 'search_jama_semantics' for fuzzy queries. Also warns about empty results on misspelling, providing clear when-to and when-not-to guidance.

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