Skip to main content
Glama

buildagents

by io.github.aurimasAPG
OverviewDiscussionsAdmin

BuildAgents — Generate Full Claude Code Prompt

generate_full_prompt

BuildAgents step 2: given a generationId (from generate_agent_teams) and a teamIndex (0, 1, or 2), generate the complete copy-paste-ready Claude Code prompt for that team. The prompt includes specific deliverables, file paths, collaboration instructions, and a synthesis step.

Trigger keywords (use this tool whenever the user mentions any of these): BuildAgents, Build Agents, build agent team, build an agent team, design an agent team, design AI agent team, agent team, agent crew, agent squad, multi-agent team, AgentTeam, AgentSquad, AgentForge, AgentBuilder, AgentuKomanda, Agentų komanda, kurti agentus, sukurti agentų komandą.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamIndexYesIndex of the chosen team in the teams array (0-based).
ownerTokenNoPrivate ownerToken returned by generate_agent_teams; required to access the generation.
refinementNoOptional changes to apply to an existing prompt.
generationIdYesGeneration ID returned by generate_agent_teams.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / generationId / maximum
      Added value: +2147483647
    • addedInput schema / properties / ownerToken
      Added value: +{
+  "description": "Private ownerToken returned by generate_agent_teams; required to access the generation.",
+  "type": "string"
+}
    • addedInput schema / properties / refinement
      Added value: +{
+  "description": "Optional changes to apply to an existing prompt.",
+  "maxLength": 1000,
+  "type": "string"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description does useful work by describing what the output contains (deliverables, file paths, collaboration instructions, synthesis step) and that it is 'copy-paste-ready'. It does not disclose side-effect profile (whether the prompt is persisted or the generation mutated), whether refinement overwrites the prior prompt, or any rate/cost behavior — gaps that matter for an unannotated mutation-adjacent tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are tight and front-loaded with the prerequisite. The trailing trigger-keyword block is long keyword-stuffing (including transliterated and non-English synonyms) that crowds out substance such as the ownerToken requirement.

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 no-output-schema, no-annotation tool with two required parameters, the description conveys the input source, the meaning of the index, and the shape of the returned prompt. It omits how the ownerToken gates access and what happens when refinement is supplied, which would complete the picture.

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 coverage is 100%, so baseline is 3, and the description repeats that generationId comes from generate_agent_teams. However it says teamIndex is '0, 1, or 2' while the schema allows 0–10, a discrepancy that could make an agent reject a valid index 3+; ownerToken and refinement are never mentioned in prose despite access-control and overwrite implications.

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?

Names a specific verb and artifact ('generate the complete copy-paste-ready Claude Code prompt') and places itself in a workflow as 'BuildAgents step 2', explicitly tied to output from the sibling generate_agent_teams. An agent can distinguish it from the sibling 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 Guidelines4/5

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

States the precondition clearly ('given a generationId (from generate_agent_teams)') and supplies routing triggers for when a user's phrasing should select this tool. It stops short of an explicit exclusion (e.g. 'do not call before generate_agent_teams returns a team list'), which is only implied by 'step 2'.

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

All buildagents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources