Skip to main content
Glama

assign_phase

Group excavation units into a phase and warn when intervening units belong to other phases, preserving stratigraphic order.

Instructions

Put units into a phase; warns if units of other phases lie between its members.

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": {
      "units": "<units>",
      "phase": "<phase>"
    },
    "name": "assign_phase"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
siteNo
phaseYes
unitsYes
authorNoagent

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/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 burden. It does disclose one genuinely useful behavior, namely that a warning is emitted when members of other phases fall between the assigned units, but it omits whether existing phase assignments are overwritten, whether the operation is reversible, what permissions or site context are required, and what the warning means for the caller.

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?

The single sentence is front-loaded and free of padding, which is good structure. However, the brevity reflects under-specification rather than disciplined concision, since essential invocation details are absent.

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?

An output schema exists, so return values need not be described, which relieves some burden. Still, for a mutation-style tool with no annotations and zero parameter documentation, the description leaves the agent without enough information about side effects, warning semantics, and parameter roles to invoke it confidently.

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

Parameters2/5

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

Schema description coverage is 0% across five parameters, so the description must compensate and largely does not. It implies the roles of 'units' and 'phase' but never clarifies expected formats (IDs vs names, single vs multiple phases), and it says nothing about 'site', 'note', or 'author', which are entirely undocumented in both places.

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 and resource: 'Put units into a phase', which tells an agent the operation assigns a set of units to a named phase. It does not differentiate this from siblings such as resolve_order, period_sequence, or above/below, and it never defines what a 'phase' is in this domain, leaving the concept ambiguous.

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 guidance on when to use this tool versus the ordering siblings (resolve_order, period_sequence, above, below), no prerequisites, and no statement about what happens if units are already assigned to another phase. The only conditional information is an implied warning, with no indication of how to react to it.

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