Skip to main content
Glama
Sign In
SAGE

SAGE

by PsYcGoD
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sage_spawn_agent

Run one focused local SAGE specialist for a bounded development task. Use only when a task clearly matches one specialization: code, test, debug, security, or performance. Returns agent_type, task, status, and a compact result.

Instructions

Run one focused local SAGE specialist for a bounded development task. Use only when a task clearly matches one specialization: code, test, debug, security, or performance. Returns agent_type, task, status, and a compact result. Side effects depend on the task: the specialist may inspect files, run local commands through SAGE, or propose edits. Do not use for open-ended chat, secrets, credentials, or tasks requiring external account access.

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": {
      "agent_type": "<agent_type>",
      "task": "<task>"
    },
    "name": "sage_spawn_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesConcrete bounded task for the specialist, including target files or command context when known.
agent_typeYesSpecialization: code (implement), test (verify), debug (investigate), security (scan), performance (optimize)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.6.2
  2. Removedv2.5.1
  3. Changed4 schema fields changedv2.4.22
    • changedInput schema / properties / agent_type / description
      Previous value: -"Type of agent to spawn"New value: +"Specialization: code (implement), test (verify), debug (investigate), security (scan), performance (optimize)"
    • changedInput schema / properties / task / description
      Previous value: -"Task description for the agent"New value: +"Concrete bounded task for the specialist, including target files or command context when known."
    • addedInput schema / properties / task / maxLength
      Added value: +1000
    • addedInput schema / properties / task / minLength
      Added value: +8
  4. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries full disclosure burden. It describes side effects ('may inspect files, run local commands, propose edits') and return format ('agent_type, task, status, and a compact result'). However, it does not detail whether changes are automatically applied or require confirmation, missing some behavioral nuance.

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?

The description is three sentences long, front-loaded with the core purpose, and contains no redundant information. Every sentence adds essential context.

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?

Given the tool's complexity (spawning an agent with side effects) and the absence of an output schema, the description adequately covers return fields, usage boundaries, and side effects. It could be improved by explicitly stating that the tool operates only on local files and commands, but 'local SAGE specialist' hints at this.

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?

The input schema already provides 100% coverage with descriptions for both parameters. The description adds minor value by noting that 'task' should include 'target files or command context when known', but this is largely a restatement of schema constraints.

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 explicitly states 'Run one focused local SAGE specialist for a bounded development task' and lists the five specializations, clearly defining the tool's purpose and distinguishing it from sibling tools that handle direct file operations or general agent interactions.

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

Usage Guidelines5/5

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

The description provides clear when-to-use guidance: 'Use only when a task clearly matches one specialization' and explicit when-not-to-use: 'Do not use for open-ended chat, secrets, credentials, or tasks requiring external account access.' This helps the agent choose appropriately among siblings.

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

Deploy Server

Other Tools