Skip to main content
Glama

log_issue

Record trial or review issues at the project rule level so corrections improve later chapters; capture a project ID and specific issue description for novel-writing pipelines.

Instructions

【规则回调】试产/评审发现的问题记录到项目规则层(07 号提醒3:改规则 = 后面 390 章都受益)。

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

Input Schema

NameRequiredDescriptionDefault
textYes问题描述(要具体:不是『改好点』而是『安排纯技术章』)
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 full burden. It does disclose one non-obvious behavioral trait: the record lands in the project rule layer and thereby affects later chapters ('改规则 = 后面 390 章都受益'), signaling a persistent, downstream-affecting write rather than a throwaway note. It does not state whether this is reversible, whether confirmation is required, or 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.

Conciseness3/5

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

It is a single short sentence, which is appropriately sized. However, the parenthetical reminder functions as a motivational aside ('07 号提醒3') rather than actionable instruction, and the bracketed tag leads with internal jargon instead of the operation itself.

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 two-parameter tool with full schema coverage and no output schema, the description covers purpose and rough trigger adequately. It leaves gaps on the consequences of logging (does it modify rule files immediately? is it queued for review?) and gives no hint of the result, which matters given the stated downstream effect.

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%, with both parameters documented in the schema itself, including the concrete 'specific not vague' example for text. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 names a concrete action and destination: record issues found in trial production/review into the project rule layer. That is a specific verb+resource an agent can act on. The bracketed label 【规则回调】 and the numbered-reminder aside are project jargon that adds framing rather than precision, but the core purpose is still legible.

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 phrase '试产/评审发现的问题' implies the trigger: use this when an issue surfaces during review or trial production. There is no explicit when-not-to-use guidance, no statement of what to do instead for other kinds of findings, and no mention of prerequisites. Usage is inferable but not spelled out.

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