Skip to main content
Glama

propose_correction

データの補正を提案する(唯一の書込ツール・人間レビュー制)。提案は即時反映されず、運営の調査と人間の承認を経て反映される。reason(提案理由)と sources(根拠となる情報ソースURL・1件以上)が必須。type別の proposedData: SONG={title?, original_artist?}(曲情報)/ SINGER={name?, description?, social_links?}(歌い手情報)/ STREAM={setlist: [{timestamp, title, artist}]}(セットリスト全置換。各要素の timestamp/title/artist はすべて非空文字列が必須 — 現在値で artist が空欄の行も、正しい原曲アーティスト名を確認して記入すること。確認できない場合は推測で埋めず提案を見送る)。現在値はサーバが公開データから取得するため送信不要。1日あたりの受付件数に上限がある。

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": {
      "type": "<type>",
      "targetId": "<targetId>",
      "proposedData": "<proposedData>",
      "reason": "<reason>",
      "sources": "<sources>"
    },
    "name": "propose_correction"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
reasonYes
sourcesYes
targetIdYes
proposedDataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false): proposals are queued for human approval rather than applied, there is a daily submission cap, and current values are fetched server-side so they must not be sent. It also flags that STREAM proposals fully replace the setlist, a material side effect the annotations do not convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Purpose, review flow, required fields, per-type payloads, and the non-guessing rule are ordered by importance in a single dense block with no filler sentences. Parenthetical nesting is heavy but every clause carries operational information an agent needs before calling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nested-object, five-required-parameter mutation tool with no output schema, the description covers nearly everything: payload shapes, validation constraints, review semantics, and rate limits. Remaining gaps are the meaning of targetId and any hint of what the call returns (proposal identifier or status), which matters since there is no output schema.

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

Parameters4/5

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

Schema description coverage is 0%, so the description carries the full burden and largely succeeds: it defines the type enum's meaning, spells out per-type proposedData shapes (SONG/SINGER/STREAM) with required non-empty fields, and states the reason and sources constraints (1+ URLs, up to the schema's max). The one gap is targetId, whose referent (song/singer/stream id) is never explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first clause gives a specific verb+resource ("データの補正を提案する") and immediately distinguishes the tool from every sibling by stating it is the only write tool ("唯一の書込ツール"). It also characterizes the mechanism (human review) up front, so an agent knows instantly what class of operation this is.

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

Usage Guidelines4/5

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

Usage context is clear: this is for proposing corrections, and the proposal is not applied immediately but goes through operator investigation and human approval. It even supplies an explicit when-NOT rule — "確認できない場合は推測で埋めず提案を見送る" — which prevents hallucinated submissions. It does not name read-side siblings (e.g. get_song) as the alternative for lookup, which keeps it short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources