Skip to main content
Glama
Local Development MCP Server

Local Development MCP Server

by lreb

search-tasks

Find tasks by keyword or phrase in titles and descriptions to quickly locate relevant items.

Instructions

Search tasks by keyword in title or description

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search-tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesKeyword or phrase to search for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely drops it. It never states that this is a read-only operation, whether matching is substring/regex/fuzzy or case-sensitive, whether multi-word queries are ANDed, or any result-count or pagination 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?

One short, front-loaded sentence with zero filler. The verb and the scope arrive immediately, and nothing is redundant.

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?

For a one-parameter search tool with a fully documented schema and no output schema, the core is covered. However, matching semantics and the read-only nature are unstated, which matters when no annotations exist to fill that gap.

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 coverage is 100% for the single 'query' parameter, so the baseline is 3. The description adds one useful detail beyond the schema: the search targets title and description fields, which tells the agent where the keyword is matched.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Search tasks') plus the search field scope ('keyword in title or description'), which distinguishes it from a plain enumeration like list-tasks. It stops short of naming a sibling or clarifying overlap with search-documents.

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

Usage Guidelines3/5

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

Usage is only implied: having a keyword to look for is the implicit trigger, versus list-tasks for browsing. There is no explicit when-to-use or when-not-to-use statement, and no mention of what to do if keyword search returns nothing.

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