Skip to main content
Glama
Sign In
agy-foreman

agy-foreman

by mountaser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

agy_status

Get status of delegation, cooldown, active jobs, and queued jobs to monitor task execution and manage job flow.

Instructions

Get status of delegation, cooldown, active and queued jobs

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": "agy_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNoRepository root path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the categories of information returned (delegation, cooldown, active and queued jobs), which implies a non-mutating inspection, but it says nothing about permissions, cost, or the shape/ordering of the response.

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?

A single front-loaded sentence with no filler. The telegraphic style ('delegation, cooldown, active and queued jobs') is dense but slightly jargon-heavy without setup.

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?

With no output schema and no annotations, the description is the only source of information about what comes back, and it only names the categories without describing the fields or structure. Adequate to select the tool, thin for interpreting its result.

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 single optional parameter 'repo' is fully described in the schema (100% coverage), so the schema does the work. The description adds no clarification about scope — e.g. whether omitting 'repo' returns status for all repositories or a default one — which is the one ambiguity worth resolving here.

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 gives a specific verb ('Get') plus an enumerated set of resources (delegation, cooldown, active and queued jobs), which tells an agent this is a state-inspection tool rather than an action. It does not explicitly contrast itself with the sibling agy_get, so the read-vs-fetch boundary is left to inference.

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 call this instead of agy_get, agy_start, or agy_act, and no prerequisites or exclusions are given. The agent must infer that 'status' means 'check state before starting or acting', which is plausible but unstated.

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