Project Tracker MCP Server

by spranab

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

search_context

Search context entries by keyword to locate relevant conversations or knowledge within project tracking data.

Instructions

Search context entries by keyword to find relevant conversations or knowledge

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": {
      "keyword": "<keyword>"
    },
    "name": "search_context"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results (default: 20)
`keyword`	Yes	Keyword to search for

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 13, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not state that this is a read-only operation, whether results are ranked or paginated, or how matches are determined (substring, full-text, semantic). 'Search' implies read-only by convention only.

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?

A single front-loaded sentence with zero filler; the action and scope come first and nothing is repeated.

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 two-parameter search with no output schema and fully documented params, the definition is minimally sufficient. It lacks any note on result shape or ranking, but the schema and absence of a return contract lower the bar.

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 keyword and limit are already fully documented with types and the default. The description adds no syntax, matching behavior, or result-count guidance beyond the schema, so baseline 3 applies.

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?

States a specific verb (search) and resource (context entries) with a qualifier (by keyword) that separates it from get_context and list_context. It does not explicitly name those siblings, but an agent can infer the distinction.

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

Usage Guidelines2/5

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

The description says what the search is for ('find relevant conversations or knowledge') but never states when to prefer it over list_context, get_context, or search_summaries/search_issues. No prerequisites, no exclusions, no alternatives are given.

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