Skip to main content
Glama

get_baseline_prompt

Get a ready-to-use test prompt for one function. Free — no subscription, no token budget, no rate limit.

Rendered deterministically from the function's AST plus its coverage rows: the signature, what to call, which exact lines never execute, which branches only go one way, what it raises, and which tests already touch it. Use this as the default way to turn "this function is untested" into "here is what to write".

get_generated_prompt is the paid, LLM-polished counterpart — it adds repo conventions and richer context, but this one is free and always available, and for most functions it is enough to write the test from.

Also accepts a React sub-unit id. The prompt then matches what the unit is: fire this handler on this element and assert the effect, or render the component in the state that takes this branch. kind and display_label come back alongside the prompt.

Errors if the function is already fully covered — there is nothing to prompt for. The exception is a covered function that no browser test and no recorded manual session has reached: that still has a real ask (drive it in a browser), so it returns a prompt saying exactly that.

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_baseline_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
function_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations present, the description carries the full burden and does so: cost and limit behavior (no subscription, token budget, or rate limit), deterministic rendering from AST plus coverage rows, and a concrete inventory of what the prompt contains. It also discloses failure semantics (errors on fully covered functions) and the exception path for covered functions no browser test or recorded session has reached.

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?

Front-loaded with the core action and the free-tier point, then the differentiation, then edge cases — a logical order. The bolded pricing/limit sentence and some of the React detail are slightly promotional, but each paragraph carries information an agent needs to select or invoke the tool correctly.

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 tool with two-tier prompt generation, React sub-unit handling, and multiple error paths, the description covers nearly all decision-relevant behavior. The one gap is the return shape: with no output schema, field names are only partially implied ('kind and display_label come back alongside the prompt').

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 coverage is 0% and the parameter has no description, so the description must compensate. It does add real meaning by stating the id may also be a React sub-unit id and that the prompt adapts to the unit type, but it never specifies the id format or where such an id is obtained, leaving a gap an agent must resolve elsewhere.

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?

States a specific verb and resource ('Get a ready-to-use test prompt for one function') and immediately pins the scope to a single function. It explicitly names and characterizes the sibling `get_generated_prompt` as the paid, LLM-polished counterpart, so an agent can distinguish the two without opening either schema.

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?

Gives an explicit default-usage rule ('Use this as the default way to turn "this function is untested" into "here is what to write"') and names the alternative with the condition that selects it (paid/richer context vs. free/always available). It also states when the tool does not apply — a fully covered function errors — and carves out the exception case where a covered-but-unreached function still returns a prompt.

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