Skip to main content
Glama

backlog_search

Search across all backlog substrates and generic resources to find relevant items. Results are ranked by relevance and include match context for quick discovery.

Instructions

Search across all indexed backlog substrates and generic resources. Returns relevance-ranked results with match context. Use this for discovery; use backlog_list for filtering by status/type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
homeNoSelect the document home for this read. "all" queries global plus the explicitly supplied/bridged project root; it never scans prior projects.
sortNoSort mode. "relevant" (default) ranks by search relevance. "recent" ranks by last updated.
limitNoMax results to return. Default: 20, max: 100.
queryYesSearch query. Supports keywords, phrases, and natural language. Fuzzy matching and semantic similarity are applied automatically.
typesNoFilter by substrate type or "resource". Default: all searchable types.
statusNoFilter entities by canonical substrate status. Default: all statuses.
parent_idNoScope search to items under a specific parent. Example: "EPIC-0001"
project_rootNoProject root for this call. Overrides the bridge project root and selects the project home.
include_scoresNoInclude relevance scores in results. Default: false.
include_contentNoInclude full content in results. Default: false (returns snippets only). Set true when you need the full text.
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does not mention side effects, permissions, rate limits, or any safety traits beyond stating it returns ranked results. This is minimal for a tool with 10 parameters and no output schema.

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?

The description is two sentences: the first sentence states purpose and return, the second gives usage guidance. It is concise, front-loaded with key information, and every sentence adds value.

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?

Despite 10 parameters and no output schema, the description provides clear usage guidance and the schema covers all parameters. It lacks details on output format beyond 'match context', but is fairly complete for a search tool given the high schema coverage.

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 100%, so the schema already documents all parameters. The description adds no extra meaning to parameters beyond the general purpose statement. Baseline score of 3 is appropriate.

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 identifies the tool as a search tool with specific verb 'Search' and resources 'backlog substrates and generic resources'. It states it returns relevance-ranked results with match context, and distinguishes from sibling 'backlog_list' by noting its use for discovery versus filtering.

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?

The description explicitly says 'Use this for discovery; use backlog_list for filtering by status/type.' This provides clear guidance on when to use this tool versus an alternative, making it easy for an agent to decide.

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/gkoreli/backlog-mcp'

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