Skip to main content
Glama

delegate_child

Issues a single-use child delegation ticket for the current session, letting a parent agent authorize a child with optional TTL and actor handle.

Instructions

Issue a single-use child delegation ticket for this session.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delegate_child"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttlNo
actor_handleNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It usefully states that the ticket is single-use and session-scoped, but it says nothing about permissions, security implications, side effects, or how the delegation is consumed.

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?

The single sentence is front-loaded and contains no wasted wording. However, its brevity reflects under-specification rather than fully earned conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a security-sensitive delegation tool with no annotations and two undocumented parameters, the description is far too thin. It omits usage conditions, parameter meaning, and behavioral details, despite having an output schema that covers return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has two parameters, 'ttl' and 'actor_handle,' with 0% schema description coverage, yet the description does not mention either parameter or explain their meaning. It therefore adds no parameter semantics beyond the field names.

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 uses a specific verb, 'Issue,' and a specific resource, 'child delegation ticket,' with the scope 'for this session.' It clearly indicates the operation, though it does not explicitly contrast this tool with any sibling.

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?

The description gives no guidance on when to use this tool, when not to use it, or what alternatives exist. The phrase 'for this session' provides scope but not actionable usage criteria.

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