Skip to main content
Glama

ecosystem_deep_review_request_batch

Queue tag-filtered ecosystem candidates for deep architecture review and return dispatch payloads for sub-agents.

Instructions

Stage 1 — Queue architecture-analysis dispatches for tag-filtered candidates.

Pulls active+shallow_done profiles whose tag set covers tags (AND semantics), creates an EcosystemDeepReview row per candidate, and returns a list of DispatchIntent payloads for backend-architect sub-agents. Leader is responsible for actually spawning each agent via the Agent tool. Each agent eventually calls ecosystem_apply_architecture_md to write back.

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

Input Schema

NameRequiredDescriptionDefault
tagsNoRequired AND-filter tags (e.g. ['memory_system', 'python']). Empty list returns 400.
limitNoMax candidates to dispatch per call (default 20).
min_starsNoOverride min_stars threshold; 0 = use project settings.
research_goalNoFree-form research-goal text injected into each sub-agent prompt (e.g. "upgrade the system memory feature").

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.2

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry the full burden; it does disclose that this is a mutation (a row is created per candidate) and that it only stages work rather than executing analysis. It does not address idempotency or duplicate handling on repeated calls, permission requirements, or whether candidate profiles are consumed or left intact — meaningful gaps for a write-side tool.

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?

The 'Stage 1' label front-loads the pipeline position and the remaining sentences each add distinct information about inputs, side effects, and handoff. Some phrasing (backticked identifiers, the closing sentence) is dense and slightly implementation-flavored, but 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?

An output schema exists, so return values need not be explained, and the description covers the pipeline handoff well. For a staging/mutation tool with zero annotations, though, it leaves out concurrency and repeat-call behavior and what happens to candidates already staged, which an agent would need to call it safely.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3; the description adds genuine meaning by clarifying the AND semantics of the tag filter and by explaining that research_goal text is injected into each sub-agent prompt. It does not add detail on limit or min_stars beyond the schema, so it is an increment rather than a full elaboration.

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 opens with a specific verb and resource ('Queue architecture-analysis dispatches for tag-filtered candidates') and then spells out the full mechanics: pulls active+shallow_done profiles whose tag set covers the tags, creates an EcosystemDeepReview row per candidate, and returns DispatchIntent payloads. This makes the tool's role in the multi-stage pipeline unambiguous and distinguishes it from the singular request sibling.

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

Usage Guidelines4/5

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

It clearly states the follow-on responsibility ('Leader is responsible for actually spawning each agent via the Agent tool') and names the closing tool each agent calls, giving the agent a clear workflow context. However, it never explicitly contrasts this batch tool with the singular 'ecosystem_deep_review_request' sibling or states when to prefer one over the other.

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

Deploy Server

Other Tools