Skip to main content
Glama

get_bulk_prompt

Return a single meta-prompt covering many items in an analysis.

scope selects which slice to aggregate:

  • untested — all functions with no tests yet

  • partial — all functions only partially covered

  • failing — all failing tests

  • everything — failing tests plus all untested + partial functions

  • frontend — TypeScript components grouped with the handlers and render branches inside them that nothing exercises yet; Playwright/React-Testing-Library oriented rather than a flat function list

Cache hits return immediately; cache misses enqueue a fresh generation and poll for up to wait_seconds. On timeout the caller gets the generation_id and can call wait_for_prompt to keep waiting.

For the common 'fix everything wrong on a branch' workflow, prefer fix_branch — it takes 'owner/repo' directly and saves the list_repositories → list_analyses chain.

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": {
      "analysis_id": "<analysis_id>",
      "scope": "<scope>"
    },
    "name": "get_bulk_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNo
scopeYes
analysis_idYes
wait_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses cache-hit vs. cache-miss behavior, that a miss enqueues a fresh generation (a side effect with cost), the polling window bounded by wait_seconds, and the timeout fallback returning a generation_id. It stops short of stating whether force bypasses the cache or whether generation has rate/cost limits.

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?

Purpose is front-loaded, the scope options are a clean bulleted list, and the operational and routing notes follow in priority order. Slightly long but no sentence is filler; the odd markup around parameter names is the only friction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter tool with no annotations and no output schema, the description covers purpose, scope semantics, async/caching behavior, and timeout recovery. The main residual gap is what the returned meta-prompt actually contains and the meaning of force.

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 0%, so the description must compensate. It fully specifies scope and implies wait_seconds ('poll for up to wait_seconds'), but analysis_id is never explained and force is not described at all, leaving two of four parameters to inference.

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 first line gives a specific verb and resource ('Return a single meta-prompt covering many items in an analysis'), and the scope bullets make the aggregation behavior concrete enough to distinguish it from get_baseline_prompt, get_generated_prompt, and fix_branch.

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

Usage Guidelines5/5

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

It enumerates all five scope values with what each selects, tells the agent to prefer fix_branch for the 'fix everything on a branch' workflow, and names wait_for_prompt as the follow-up on timeout. That is explicit when-to-use and when-to-use-something-else guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources