Skip to main content
Glama

get_generated_prompt

Return a meta-prompt for writing tests for the function.

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

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": {
      "function_id": "<function_id>"
    },
    "name": "get_generated_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNo
function_idYes
wait_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it discloses cache-hit vs cache-miss behavior, that a miss enqueues a generation and polls for up to wait_seconds, and that a timeout yields a generation_id. It stops short of disclosing what force does, whether generation is billed/rate-limited, or what happens on invalid function_id.

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?

It is short, front-loaded with the purpose, and the async/timeout caveat follows in a logical order without filler. The line-broken phrasing is slightly awkward 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?

For a three-parameter tool with no annotations and no output schema, the definition explains the waiting/timeout mechanics well enough to call it correctly, but leaves the return shape of the meta-prompt and the semantics of force undocumented. It is adequate rather than complete.

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%, so the description must carry all parameter meaning, yet it only implicitly addresses wait_seconds through the polling narrative. The required function_id and the force flag are never explained — force in particular is a mutation-shaped knob whose effect an agent cannot guess.

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 and resource ('Return a meta-prompt for writing tests for the function'), which an agent can act on. It does not, however, distinguish this from similarly named siblings such as get_baseline_prompt or get_bulk_prompt, leaving the agent to infer the difference from the names alone.

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 implied by the caching/polling narrative, and there is one explicit routing rule: on timeout, call wait_for_prompt to keep waiting. That is real guidance, but only for the failure branch — nothing states when to prefer this tool over get_baseline_prompt or get_bulk_prompt, and no exclusions are given.

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