Skip to main content
Glama

misakanet_submit_usage

Record that a MisakaNet lesson solved your problem. Submit the lesson ID, tool, and outcome after using a fix to track which lessons help.

Instructions

[Experimental] Record that a public lesson helped with a problem. Call this AFTER a lesson has been used and the outcome is known — use misakanet_usage_status to check remaining quota before submitting. Input semantics: lesson_id is required (the lesson that helped); tool names the calling client (e.g. 'claude-code', 'cursor'); outcome should be solved, partial, not-helpful, or another short status. Output schema: JSON with {lesson_id, tool, outcome, status}. Error cases: missing lesson_id. Side effects: currently returns a local placeholder report only (remote submission is disabled when MISAKANET_USAGE_DISABLE_REMOTE=1). Auth: none. Rate limits: local stdio process only.

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": {
      "lesson_id": "<lesson_id>"
    },
    "name": "misakanet_submit_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNoCalling tool or client name, for example claude-code, cursor, codex, or aider.
outcomeNoShort result label such as solved, partial, or not-helpful.
lesson_idYesRequired ID of the lesson that helped, for example auto-merge-ci-pipeline.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.14.0
    • changedInput schema / properties / lesson_id / description
      Previous value: -"ID of the lesson that helped (e.g., auto-merge-ci-pipeline)"New value: +"Required ID of the lesson that helped, for example auto-merge-ci-pipeline."
    • changedInput schema / properties / outcome / description
      Previous value: -"Outcome: solved, partial, not-helpful"New value: +"Short result label such as solved, partial, or not-helpful."
    • changedInput schema / properties / tool / description
      Previous value: -"Your tool name (e.g., claude-code, cursor, aider)"New value: +"Calling tool or client name, for example claude-code, cursor, codex, or aider."
  2. Addedv2.12.4
  3. Removedv2.12.2
  4. First observedv2.12.3

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past annotations: discloses that only a local placeholder report is produced while remote submission can be disabled via MISAKANET_USAGE_DISABLE_REMOTE, states auth is none, scopes rate limits to a local stdio process, and enumerates the error case (missing lesson_id). These are exactly the side-effect and environment facts an agent cannot get from readOnlyHint/destructiveHint alone.

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?

Front-loads the purpose, then sequences the prerequisite, input semantics, output shape, errors, side effects, auth, and limits in labeled clauses. Dense but nearly every clause carries new information; the '[Experimental]' tag and repeated output-field listing are the only near-redundancy.

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

Completeness5/5

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

No output schema exists, yet the description supplies the return JSON keys, the single failure mode, the placeholder-vs-remote side effect, and the auth/rate-limit posture. For a 3-parameter tool this leaves no material gap for correct invocation.

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 100%, so the schema already documents all three parameters. The description restates the same value examples for outcome and the same role for tool without adding syntax, constraints, or defaults beyond them, so the baseline of 3 applies.

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?

States a specific verb and resource ('Record that a public lesson helped with a problem') and scopes it to post-hoc reporting, which separates it from misakanet_search, misakanet_get_lesson, and misakanet_write_lesson. The 'AFTER a lesson has been used' framing makes the distinction operational rather than descriptive.

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

Usage Guidelines5/5

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

Explicitly specifies the triggering condition ('AFTER a lesson has been used and the outcome is known') and names the sibling to consult first (misakanet_usage_status for remaining quota). The pre-check ordering is stated, not inferred.

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