Skip to main content
Glama

repo_review_queue

Read-onlyIdempotent

List pending memory proposals and stale approved memories needing fresh context to help coding agents review and refresh outdated repository knowledge.

Instructions

List pending memory proposals and stale approved memories that need fresh context.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

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 this safe, idempotent, closed-world read, so the safety profile is fully covered and the description only needs to add scope. It does add that the result spans two distinct memory categories, which is useful. It does not define what makes a memory 'stale', how results are ordered, or whether the list is paginated.

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?

One compact sentence, front-loaded with the verb and both result categories, with no filler. The only slight looseness is the vague qualifier 'need fresh context', which is not defined.

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 read-only lister with complete annotations and one optional parameter, the description covers purpose but leaves the return shape undefined, and no output schema exists to compensate. It should at least say what each entry contains (e.g., proposal text, staleness reason) and how limit interacts with the result set.

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?

There is a single parameter, limit, with 0% schema description coverage; the schema supplies only type and a default of 50. The description never mentions the parameter, its maximum, or what happens when more items exist than the limit, so it adds no meaning at all beyond the raw schema.

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 gives a specific verb ('List') and a clearly bounded resource: pending memory proposals plus stale approved memories needing refresh. An agent knows exactly what comes back at a category level. It stops short of distinguishing itself from adjacent read tools such as repo_memory_audit or repo_team_memory_search.

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: the word 'pending' and 'need fresh context' suggest this is the triage entry point before acting via repo_approve_memory or repo_reject_memory, but no alternative is named and no when-not condition is given. An agent can infer the workflow but must guess the boundaries.

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