Skip to main content
Glama

Report a mission skipped

mission_skipped

Reports a mission you didn't send because one of its stop rules held: they already answered, the thread is gone, their messages are closed, or they asked not to be contacted (then Marsell never contacts them again). Say why in plain words and which rule in stop.

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": {
      "mission_id": "<mission_id>",
      "why": "<why>"
    },
    "name": "mission_skipped"
  }
}

Input Schema

NameRequiredDescriptionDefault
whyYesWhat you saw, in plain words.
stopNoWhich stop rule held.
projectNoThe project's id or exact name. Optional when the account has one project.
sessionNoA short name for this session of yours (letters, digits, dots, dashes, colons or underscores, up to 64), made up once when this wake starts and passed the same to missions_next and every report. A mission is held for the session that took it: another session gets a different one, or hears when to come back, and only the session that took a mission reports it.
mission_idYesThe mission's id from missions_next (ms- and 16 hex characters).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare that this is a non-read-only, non-open-world, non-destructive call; the description adds the material consequence that one rule, 'asked_not_to_be_contacted', means Marsell never contacts them again. That durable side effect is exactly the kind of context annotations cannot convey. It does not cover retry/idempotency behavior or what happens if the same mission is reported twice.

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?

Two sentences, front-loaded with the trigger condition, and the parenthetical earns its place by disclosing the durable no-contact effect. The trailing clause 'Say why in plain words and which rule in stop' slightly duplicates schema text and could be trimmed.

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 5-parameter, 2-required reporting tool with full schema coverage, no output schema, and modest annotations, the description supplies purpose, trigger conditions, and the key downstream consequence. No material gap remains for an agent to call it correctly.

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%, including a documented enum for 'stop' and a precise format note for 'mission_id' and 'session', so the schema already carries the parameter burden. The description only restates it ('Say why in plain words and which rule in stop') without adding format, validation, or conditional-presence guidance. Baseline 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 ('Reports a mission you didn't send') and scopes it to a well-defined trigger set, then enumerates all four stop rules. An agent can immediately distinguish this from mission_done (mission was sent) or mission_stuck without opening any 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?

The when-to-use condition is explicit and exhaustive: one of the four stop rules held, each named in plain language. It stops short of explicitly routing to siblings ('if the mission was actually sent, use mission_done'), so the agent must infer the alternative, but the trigger condition itself leaves nothing ambiguous.

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.