Skip to main content
Glama

misakanet_me_events

Read-onlyIdempotent

Verify whether a lesson was actually reused by real clients. Returns E4 evidence from observed retrieval requests, distinguishing proven reuse from citations or votes.

Instructions

[READ-ONLY EVIDENCE] Return evidence of a lesson being reused. E4 is observed reuse: search_signals shows two or more distinct clients actually retrieved the lesson — a count of requests, never of prose. Regression-benchmark citations, helpful votes and a lesson's own verified by: line are E3 hints: a citation is sandbox-level evidence, a vote is one person's opinion, and a provenance line is the lesson talking about itself, so none of them can confer E4. Use to check whether a lesson is proven by real usage, not just self-reported. Provide lesson_id or lesson_path — if neither is supplied the tool returns {error}. Semantically 'misakanet_get_my_events' (evidence for the lessons your node submitted/used); kept as me_events for backward compatibility. No auth required (read-only, rate-limited). Returns: object {lesson_id, events: [{type, count|queries|sources, evidence_level}], evidence: 'E0'|'E3'|'E4', note}. Example: misakanet_me_events(lesson_id='dco-auto-fix-workflow') Input semantics: lesson_id (filename stem, e.g. dco-auto-fix-workflow) or lesson_path (e.g. lessons/core/dco-auto-fix-workflow.md) — the endpoint derives the id from the path the same way. Passing neither is refused before any network call. Output schema: proxied unchanged from the hosted tool (lesson_id, events[], evidence, note). Error cases: missing_lesson_reference when both arguments are absent; hosted_endpoint_unavailable when the hosted service cannot be reached or refuses the call — this is a proxy, so there is no local fallback, and an empty events list would be a different, wrong answer. Side effects: none (read-only, no local writes). Auth: none. Rate limits: the hosted endpoint's anonymous read burst window applies; the proxy adds no local limit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "misakanet_me_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
lesson_idNoLesson ID (filename stem), e.g. dco-auto-fix-workflow. Either lesson_id or lesson_path is required.
lesson_pathNoOptional full path, e.g. lessons/core/dco-auto-fix-workflow.md. Either lesson_id or lesson_path is required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.5.0
    • removedInput schema / oneOf
      Removed value: -[
      -  {
      -    "required": [
      -      "lesson_id"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "lesson_path"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "lesson_id",
      -      "lesson_path"
      -    ]
      -  }
      -]
  2. Changed2 schema fields changedv2.43.0
    • removedInput schema / minProperties
      Removed value: -1
    • addedInput schema / oneOf
      Added value: +[
      +  {
      +    "required": [
      +      "lesson_id"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "lesson_path"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "lesson_id",
      +      "lesson_path"
      +    ]
      +  }
      +]
  3. Addedv2.40.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds material context the annotations cannot: no auth, anonymous rate burst window on the hosted endpoint, and that this is a pure proxy with no local fallback, so an empty events list would be a distinct and wrong answer. It also enumerates error modes (missing_lesson_reference, hosted_endpoint_unavailable) and states side effects are nil.

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?

The purpose and the E3/E4 distinction are front-loaded, which is right, but the block is heavy and repeats itself: read-only/no-local-writes appears three times, and the null-argument refusal is stated twice. The 'Returns', 'Output schema', and 'Example' lines also restate one another, so several sentences do not fully earn their place.

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?

For a two-optional-parameter proxied read, it covers return shape, evidence-level semantics, argument fallback, error cases, auth, rate limits, and side effects. Nothing an agent needs in order to call it correctly or to interpret a failure is missing.

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 coverage is 100%, so the baseline is 3, but the description adds that lesson_id is a filename stem and that the endpoint derives the id from lesson_path the same way they are given. It also clarifies the validation timing — passing neither is refused before any network call — which is behavior rather than restatement of the schema.

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 — returns evidence that a lesson was reused — and precisely defines what qualifies as E4 (two or more distinct clients retrieving the lesson) versus E3 hints (citations, votes, provenance lines). An agent can distinguish this from retrieval tools like misakanet_get_lesson or misakanet_search without opening a schema.

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?

Gives a clear decision rule: 'Use to check whether a lesson is proven by real usage, not just self-reported.' It also pre-empts a common misuse by explaining why citations, votes, and `verified by:` lines cannot be treated as E4. It stops short of naming a sibling to use instead for the non-reuse case, which keeps it off a 5.

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