Skip to main content
Glama

misakanet_me_inbox

Read-onlyIdempotent

Check a previously submitted intake's status by intake_id or dedup_key without resubmitting it; this read-only lookup returns answered, pending, converted, or unknown.

Instructions

Check the status of a previously submitted intake (question, missing_lesson, ...) without re-submitting it. The read is served by the hosted endpoint; an intake still sitting in the local contribution queue is answered from there (delivery=local_queue), because no hosted lookup can see it. Input semantics: provide intake_id (e.g. 'issue-1234' or '1234') or dedup_key from misakanet_submit_intake. At least one is required. Output schema: {intake_id, status, answer?, lesson_id?, issue_url?, note}. status is one of answered, pending, converted, unknown — 'unknown' means the lookup could not determine it, which is a different answer from 'never happened'. Error cases: missing both intake_id and dedup_key returns {error, hint}; an unreachable endpoint returns status=unknown with error=hosted_endpoint_unavailable, never a false not_found. Side effects: none — this is a read-only call. Auth: none. Rate limits: none of its own — the hosted endpoint's read burst limit applies to the forwarded call.

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_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
dedup_keyNoThe dedup_key (8-char FNV-1a hex key) from a prior submit_intake response. Either intake_id or dedup_key is required.
intake_idNoQuestion intake ID from a prior submit_intake response, e.g. 'issue-1528' or '1528'; for non-question intakes use dedup_key. Either intake_id or dedup_key is required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.5.0
    • changedInput schema / properties / dedup_key / description
      Previous value: -"The dedup hash from misakanet_submit_intake response (e.g. 'def456')."New value: +"The dedup_key (8-char FNV-1a hex key) from a prior submit_intake response. Either intake_id or dedup_key is required."
    • changedInput schema / properties / intake_id / description
      Previous value: -"The intake ID from misakanet_submit_intake response (e.g. 'abc123')."New value: +"Question intake ID from a prior submit_intake response, e.g. 'issue-1528' or '1528'; for non-question intakes use dedup_key. Either intake_id or dedup_key is required."
  2. Addedv2.43.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses the local_queue fallback path and why it exists, the full status vocabulary including the semantic difference between 'unknown' and 'never happened', the missing-parameter error shape, and the guarantee that an unreachable endpoint yields error=hosted_endpoint_unavailable rather than a false not_found. Auth and rate-limit behavior are also stated. That is a materially richer behavioral picture than readOnlyHint/idempotentHint alone provide.

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-loaded with purpose, then organized into labeled sections (Input semantics, Output schema, Error cases, Side effects, Auth, Rate limits) that map to what a caller needs. It is on the dense side and repeats the schema's 'either is required' constraint twice, but no sentence is filler.

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 read-only lookup with two optional params and no output schema, the description covers the return shape, the status enum semantics, error paths, and the local-queue edge case — the exact ambiguity (unknown vs. not_found) that would otherwise cause an agent to misreport a result. Nothing needed to call it correctly 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 already 100%, so the baseline would be 3, but the description adds selection logic the schema only hints at: intake_id accepts 'issue-1234' or '1234', non-question intakes require dedup_key, and at least one of the two must be supplied. That is genuine disambiguation between the two parameters rather than a restatement.

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 description opens with a specific verb and resource ('Check the status of a previously submitted intake') and immediately scopes it with 'without re-submitting it', which is exactly the distinction from the sibling misakanet_submit_intake. An agent can tell which of the two tools to pick from the first sentence alone.

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: call this to poll the state of an intake already submitted, and pull dedup_key from misakanet_submit_intake rather than generating one. It does not add an explicit exclusions statement (e.g. 'do not use to submit'), but the 'without re-submitting' framing makes the alternative implicit and unambiguous.

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