Skip to main content
Glama
Sign In
agy-foreman

agy-foreman

by mountaser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

agy_start

Starts an implement or explore delegation job, sending plan tasks to Gemini in isolated worktrees and gating merges on verified test results.

Instructions

Start an implement or explore delegation job

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": {
      "kind": "<kind>"
    },
    "name": "agy_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesTask kind
planNoPlan step specification
repoNoRepository root path
taskNoTask description
effortNoEffort level
skillsNoSkills to use
dry_runNoDry run flag
base_refNoBase git ref
estimateNoToken estimate
timeout_secNoTimeout in seconds
contract_testsNoContract tests

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden and fails: nothing is said about side effects, whether the job runs synchronously or returns a handle, what dry_run actually prevents, permission/auth needs, or what happens on timeout. Only the bare implication of starting work is conveyed.

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

Conciseness3/5

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

One front-loaded sentence with zero wasted words, but it is under-specified for a tool with 11 parameters and nested objects rather than appropriately sized. Brevity here is a symptom, not a virtue.

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

Completeness2/5

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

For a job-launching tool with nested plan/estimate/contract_tests objects, no annotations, and no output schema, the description omits nearly everything an agent needs: relationship between kind and plan, whether repo/task are required in practice, and what a successful start produces.

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 schema documents all 11 parameters and baseline 3 applies. The description adds no meaning beyond the schema, and several schema descriptions ('Task kind', 'Effort level', 'Skills to use') remain thin, with no help on how plan, estimate, and contract_tests relate to each other.

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 verb 'Start' plus the enumerated kinds ('implement or explore') give a concrete action and distinguish it from sibling verbs agy_status/agy_get/agy_act. The object 'delegation job' remains unexplained jargon, but an agent can tell this creates a job rather than inspecting or acting on one.

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?

There is no statement of when to choose this over agy_act, agy_status, or agy_get, nor any prerequisites such as needing a repo, a plan file, or an existing plan step. The parameter list implies context but the description supplies no routing guidance.

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