Skip to main content
Glama
UditMahaldar

HP ALM MCP Server

by UditMahaldar

alm_search

Execute HPQL search across ALM entities such as defects, tests, and requirements. Apply filters and specify return fields.

Instructions

Generic HPQL search across any ALM entity collection.

Use this for advanced queries not covered by the specific tools above.

Args: entity_type: ALM entity collection — e.g. 'defects', 'tests', 'requirements', 'test-sets', 'test-instances', 'runs', 'test-folders'. query: HPQL filter string (without braces). Examples: "status[Open];severity[4-Very High]" "name[login]" "owner[jsmith];creation-time[> '2026-01-01']" "owner[u1197976];parent-id[2400]" ← filter tests by folder + owner Leave empty to return all entities up to page_size. NOTE: For 'tests', use 'parent-id' to filter by folder — there is no 'subject' field. Combining 'parent-id' with multiple OR values (e.g. parent-id[1|2|3]) may cause HTTP 500 on some ALM servers; query each folder separately in that case. fields: Comma-separated ALM field names to include in the response. Example: 'id,name,status,owner,creation-time' For 'tests': valid fields include id,name,status,owner,parent-id, creation-time,subtype-id,description. 'subject' is NOT a valid field. page_size: Maximum records to return (default 100).

Returns: {"entity_type", "results": [...], "count": }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entity_typeYes
queryNo
fieldsNoid,name
page_sizeNo
Behavior4/5

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

Despite no annotations, the description discloses return format, query limitations (HTTP 500), and valid fields for tests. It would benefit from mentioning read-only nature, but overall transparent for a search 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 sections, front-loaded purpose, and necessary details. Slightly long but justified due to complexity and need for examples. Could tighten some example text slightly.

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 31+ sibling tools, description clearly positions itself for advanced queries. Covers all parameters, return format, and known limitations. No output schema but return structure described. Sufficient for agent to understand tool's role.

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%, but description provides extensive semantics: entity_type with examples, query with detailed examples and notes on syntax and limitations, fields with examples and valid field list, page_size with default. This fully compensates for schema's lack of 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?

The description clearly states it performs HPQL search across any ALM entity collection, with the verb 'search' and resource 'any ALM entity collection'. It distinguishes itself from sibling specific tools by targeting advanced queries not covered elsewhere.

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 states 'Use this for advanced queries not covered by the specific tools above', providing clear when-to-use guidance. Includes caveats like HTTP 500 for multiple OR values and recommends querying each folder separately, offering when-not-to and alternatives.

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/UditMahaldar/opentext-alm-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server