Skip to main content
Glama
Sign In

AgentLair

by io.github.piiiico
OverviewDiscussionsAdmin

delegate_task

Delegate a task to another AgentLair agent. The task is delivered to the agent's inbox and picked up asynchronously. Use this when you need another agent to do something — send an email, run a deployment, do research, etc.

Input Schema

NameRequiredDescriptionDefault
toYesTarget agent's AgentLair email (e.g. pico@agentlair.dev)
taskYesWhat to do — be specific and self-contained. The receiving agent has no context from your conversation.
contextNoBackground information the agent needs to execute the task
priorityNoTask priority (default: normal)
constraintsNoTiming constraints, requirements, or limits

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Discloses async delivery and lack of context sharing, which are key behavioral traits. No annotations provided, so description carries full burden; could mention completion notification, failure modes, or guarantees.

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?

Two efficient sentences: first states purpose+mechanism, second gives usage guidance. Front-loaded and waste-free.

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?

Covers core behavior and usage context well. Missing output schema details (e.g., task ID returned) but functional for a delegation tool.

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 has 100% coverage with clear parameter descriptions. The tool description adds no extra meaning beyond schema; thus baseline 3 is appropriate.

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?

The description clearly states the tool's purpose: delegating tasks to another AgentLair agent. It differentiates from sibling tools (calendar, email, vault) that perform direct operations, establishing a distinct role.

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?

The description explicitly says 'Use this when you need another agent to do something' with examples (send email, deployment, research). Does not enumerate alternatives or cases where not to use, but context is clear enough.

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

All AgentLair 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