Skip to main content
Glama

repo_team_memory_search

Read-onlyIdempotent

Search approved team memories checked out from Git to retrieve shared context for coding tasks; local and private staged memories are excluded.

Instructions

Search approved team memories checked out from Git; local/private staged memories are not included.

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": "repo_team_memory_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.6

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety bar is largely met. The description adds genuinely useful provenance context – only approved memories from Git, staged/private ones excluded – which tells the agent results may be incomplete relative to local work. It says nothing about ranking, matching behavior, or result size relative to limit.

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?

A single front-loaded sentence with no filler; the key scope constraint is stated immediately. Slightly dense phrasing ('checked out from Git') without further elaboration, but nothing is wasted or buried.

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 simple 2-parameter read tool with strong annotations and no output schema, the definition covers the core scope question but leaves query syntax and limit semantics entirely undetermined. An agent can invoke it, but not confidently tune the call or interpret truncated results.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters, so the description carries the full burden and does not meet it. It never explains what 'query' matches (memory text, tags, paths?) or how 'limit' (default 10) behaves, leaving an agent unable to predict result shape or refine searches.

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 (approved team memories), plus a scoping detail: memories checked out from Git. It distinguishes this corpus from local/private staged memories, which separates it from sibling tools like repo_stage_memory or repo_approve_memory, though it doesn't name an alternate search tool explicitly.

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?

Use is implied by the 'approved / Git-checked-out' scope, and the description explicitly notes what is NOT included (local/private staged memories). However, it gives no explicit when-to-use vs. when-to-use-another-tool guidance, so an agent must infer that unpublished memories are unreachable from this tool.

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