Skip to main content
Glama

Recruit an agent into the room

recruit

Create a named AI teammate backed by an OpenRouter model. Validates the model ID against the OpenRouter catalog so the role is ready to join your chat sessions.

Instructions

Create a named recruit backed by an OpenRouter model. Validates the model id against the OpenRouter catalog.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYeslowercase handle, 2-24 chars: ^[a-z0-9_-]{2,24}$
tagsNotopic tags, e.g. ["security","rust"]
modelYesOpenRouter model id, e.g. "openai/gpt-4o-mini", or a local one: "local/ollama/<model>" / "local/llama-server/<model>"
watchNowhen true, this recruit reviews each of your turns at Stop and may leave a comment; costs one call per turn
paramsNoextra completion params (temperature, max_tokens, ...)
autonomyNohow far this seat may act on its own (default L0). L0 advise-only: proposes, never acts. L1 reversible acts. L2 impactful but rollbackable, and they name the rollback first. L3 needs an explicit human yes before any action. Shown on the roster and exported into hermes.
briefingNoONBOARDING BRIEF, 10-20 lines, written by YOU from everything you know that they cannot see: the project and its goal, where it stands now, the decisions already taken, a glossary of local codenames, and what this role is expected to do. It is injected into every call. Omit it and they start cold.
system_promptYesthe persona: who they are and how they should think
fallback_modelNomodel to retry on when the primary is rate limited or erroring. For a local recruit this is also what runs when their server is down — omit it and calls report the server-down message instead of going remote.
authoring_ratingNoYOUR self-rating of the system prompt you just wrote, 1-10 per dimension. The overall is the MINIMUM, not the mean; below 9 you should have revised the weakest dimension once before hiring.
Install Server

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It adds one genuinely useful behavioral trait — 'Validates the model id against the OpenRouter catalog' — which goes beyond the schema. However, it omits failure modes, upfront cost or usage implications, side effects on the room/roster, and what is returned, which matters for a mutating creation tool.

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

Conciseness5/5

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

Exactly two sentences with no wasted words; the core action is front-loaded and the validation disclosure earns its place. Exemplary conciseness.

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?

The tool is complex (10 parameters, nested objects, no output schema), and while the schema carries heavy detail, the description leaves real gaps: no sense of the creation outcome, no cost/usage caveats, and no differentiation from audition. Adequate but with clear holes.

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 100%, so the baseline of 3 applies. The description adds validation context for the model parameter but otherwise relies on the schema's rich parameter descriptions, which already document formats, defaults, enum semantics, and constraints thoroughly.

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 states a specific verb and resource ('Create a named recruit backed by an OpenRouter model'), clearly identifying the action and object. It is distinguishable from siblings like dismiss or update_persona, though it does not explicitly differentiate from audition, its nearest alternative.

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

Usage Guidelines2/5

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

No guidance is given on when to recruit versus audition or update_persona, and no exclusions or prerequisites are stated. An agent must infer usage from the title and sibling names rather than from the description itself.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/arizqi/teambrrr'

If you have feedback or need assistance with the MCP directory API, please join our Discord server