Skip to main content
Glama

tracker_search_issues

Read-only

Search Tracker issues without modifying them using filters, AND/OR combinations, or an advanced query; returns compact results and text search matches titles only.

Instructions

Search Tracker issues without modifying them. Use individual filters combined with AND, OR an advanced Tracker query. text searches titles only. status accepts status key/name, assignee accepts login or ID (not an ambiguous display name). Returns compact results; use tracker_get_issue for details. Follow nextPage explicitly.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tracker_search_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
textNo
queryNo
queueNo
statusNo
perPageNo
assigneeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description still adds real behavior: results are compact, pagination must be followed via nextPage. It does not mention permissions, rate limits, or result ordering, which keeps it short of a 5.

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?

Front-loaded with purpose, then filters, then field semantics, then the sibling hand-off and pagination note — every sentence carries information. The telegraphic fragments ("text searches titles only") trade grammar for density but remain parseable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With seven parameters at 0% schema coverage and no output schema, the description would need to cover more ground; it handles text, status, assignee and query but leaves queue undefined. The instruction to "follow nextPage explicitly" is also underspecified given the schema exposes only page/perPage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does explain three fields with real semantics: text matches titles only, status accepts key or name, assignee accepts login/ID but not display name. However, queue is never explained and page/perPage are only vaguely alluded to via "nextPage," leaving several of seven parameters undocumented anywhere.

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?

States a specific verb and resource ("Search Tracker issues") plus scope ("without modifying them"), and explicitly separates itself from the sibling that fetches full records: "use tracker_get_issue for details." An agent can pick between search and get without opening either schema.

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?

Gives concrete composition guidance ("individual filters combined with AND, OR an advanced Tracker query") and names the details alternative, tracker_get_issue. It lacks explicit when-not-to-use exclusions (e.g., single-issue lookup or user resolution) but the routing intent is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.