Skip to main content
Glama
yyy188
by yyy188

find_jama_project_by_name

Find Jama projects by a full or partial name to retrieve their numeric ID and metadata, enabling subsequent operations like listing releases or test runs.

Instructions

Find Jama projects by name (case-insensitive) and return their info.

Useful when you only know a project's name (or a fragment of it) and need
its numeric id to feed into other tools (init_jama_project,
list_jama_releases, list_jama_test_runs, …). Matching is substring by
default; pass exact=True for full case-insensitive equality.

Args:
    name: project name or fragment (e.g. "acre" matches "Acrelec").
    exact: if True, require full case-insensitive name equality.
    limit: max matches to return (default 20).

Returns:
    {"count","results":[{id,project_key,name,status,description}, ...]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
exactNo
limitNo
Behavior4/5

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

Discloses case-insensitive and substring matching behavior, plus the effect of exact parameter. Describes return format. No annotations provided, so description carries full burden; it adequately covers key traits but could mention if operation is read-only (likely) and any rate limits.

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?

Well-organized with Args and Returns sections. Front-loaded purpose in first line. Every sentence adds value; no redundancy.

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?

Given no annotations or output schema, description fully covers tool purpose, parameter behavior, return format, and usage context for downstream tools. No gaps for this simple lookup tool.

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 significant value beyond schema: explains name is a fragment by default, exact parameter controls full match, limit caps results. Schema has 0% description coverage, so description fully compensates with detailed semantics and examples.

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?

Clearly states verb 'Find' and resource 'Jama projects by name', with case-insensitive matching. Distinguishes from sibling list_jama_projects by focusing on name-based lookup to get IDs for other tools.

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 says when to use: when only project name is known and numeric ID is needed for other tools. Provides context on substring vs exact matching. Could be improved by explicitly stating when not to use (e.g., if ID already known), but implication is clear.

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