Fine Structure

Create Agent Team

create_agent_team

Create a whole team of agents from a template, wired to work together, optionally adapted to the owner's requirements and company name. The new agents start active with the platform's default safe permissions and can message only their verified owner until channels are connected in Fine Structure.

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": {
      "template": "<template>"
    },
    "name": "create_agent_team"
  }
}

Input Schema

Name	Required	Description
`lang`	No	Language of the catalog text, e.g. en or he.
`template`	Yes	A template key from list_team_templates.
`company_name`	No
`requirements`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, open-world behavior, so the description earns credit for adding real context beyond them: new agents start active with default safe permissions, are restricted to messaging only the verified owner, and remain so until channels are connected in Fine Structure. It does not address duplicate-creation behavior on repeat calls or failure/partial-creation semantics.

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?

Two sentences, front-loaded with the action and the template source dependency, followed by the post-creation state. Some flavor phrasing ("wired to work together", "Fine Structure") is slightly atmospheric but still conveys information.

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 mutating bulk-creation tool with annotations covering the safety profile and a mostly-documented schema, the description covers origin, adaptation inputs, and resulting agent state. What remains missing is what the call returns (team/agent identifiers) and whether partial failure can occur — but no output schema exists to offset that.

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 50%: lang and template are documented in-schema, while company_name and requirements are bare. The description partially compensates by explaining those two as optional adaptations to owner requirements and company name, but adds no syntax, limits, or effect details for them.

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?

"Create a whole team of agents from a template" gives a specific verb and resource, and "wired to work together" signals this is a bulk/multi-agent creation rather than the single-agent create_agent sibling. It stops short of naming list_team_templates (the source of the template key) or any alternative explicitly in the description text.

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: you must have a template, and it is "optionally adapted" via requirements/company name. The prerequisite of first calling list_team_templates appears only in the parameter schema, not the description, and there is no when-not guidance (e.g., when to use create_agent instead).

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

All Fine Structure tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?