Skip to main content
Glama

advance_sop

Marks a specified SOP step complete for a project, enforcing the required 1→7 order so novel-writing pipelines stay on track.

Instructions

标记某一步 SOP 完成(须按 1→7 顺序)。

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": {
      "project_id": "<project_id>",
      "step": "<step>"
    },
    "name": "advance_sop"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepYes
project_idYes项目 ID(内部代号,如“默者”)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It discloses the sequential-ordering behavior, which is genuine behavioral context beyond the schema's 1-7 bounds, but omits what happens on a violation (error? silent?), whether re-marking is idempotent, and what the call returns.

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 tightly packed sentence with the constraint front-loaded and zero filler. It is efficient, though so terse that it leaves real behavioral questions unanswered.

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 mutation tool with no annotations and no output schema, the definition says little about failure modes, permission requirements, or result shape. The ordering constraint helps, but an agent attempting an out-of-order or duplicate call has no guidance.

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 coverage is 50%: project_id is documented in the schema while step is not. The description partially compensates by tying step to the 1-7 sequence, but adds no format or identity semantics for project_id beyond the schema's example.

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?

States a specific verb+resource: marking a specific SOP step as complete. The agent can tell this is a write action on SOP state, distinguishable from a status-reading sibling like sop_status, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

The parenthetical '须按 1→7 顺序' gives a real precondition (steps must be advanced in order), which is useful usage guidance. However, it does not say when to prefer this over checking sop_status first, nor what to do on out-of-order attempts.

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