Skip to main content
Glama

sop_status

Check a project's 7-step new-book SOP progress and per-step checklists to see completion status and identify outstanding tasks.

Instructions

查看开新书 7 步 SOP 进度与各步检查清单(07 号)。

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>"
    },
    "name": "sop_status"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does convey that this is a non-mutating inspection of progress plus per-step checklists. It says nothing about whether an unknown or uninitialized project_id errors, whether progress starts implicitly, or what shape the response takes.

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 tight sentence with the object of the lookup front-loaded and no filler. The parenthetical '(07 号)' is an unexplained internal document reference that costs a little clarity without adding usable meaning.

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?

For a simple one-parameter read tool this is nearly adequate, and the schema covers the only input. But with no output schema and no return-value detail, the agent cannot tell what the checklist payload looks like or how progress is represented.

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?

Only one parameter, and the schema already documents project_id fully at 100% coverage with a pattern and an example. The description adds no further meaning about that parameter, so this sits at the baseline for a schema-covered single-param tool.

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 uses a specific verb (查看, 'view') plus a specific resource (开新书 7 步 SOP 进度与各步检查清单) and scopes it to document 07. An agent can distinguish this read/status tool from advance_sop without opening either schema, though the sibling is never named.

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?

Usage is only implied: 'view progress' suggests a read-only status check, in contrast to the mutation-flavored advance_sop. There is no explicit when-to-use, no when-not-to-use, and no stated alternative for advancing or fetching a brief.

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