Skip to main content
Glama

Axad

Finish a step

record_step

Record how the current step of a learning path went (done, skipped or struggled) with an optional note, and move the learner on. Returns the next step, or that the path is finished.

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": {
      "runbook": "<runbook>",
      "lang": "<lang>",
      "step": "<step>",
      "outcome": "<outcome>"
    },
    "name": "record_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
langYes
noteNoWhat the learner found hard, in a few words.
stepYesThe current step's id.
outcomeYes
runbookYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations mark this as a non-read-only, non-idempotent mutation, and the description adds meaningful context beyond them: the call has a progression side effect ('move the learner on') and returns the next step or a finished-path signal. It does not warn about repeat-call behavior or errors for an invalid/stale step, which is the main remaining gap for a non-idempotent write.

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?

Two dense sentences with zero filler: the action and outcome options come first, followed by the return contract. Nothing is repeated from the title and no sentence is wasted.

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

Completeness3/5

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

For a mutating tool with no output schema, the description does state the return contract, which is valuable. However, with 5 parameters, 40% schema coverage, and two wholly undocumented required inputs, the definition is not complete enough for an agent to call it confidently without inspecting external docs.

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

Parameters2/5

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

Schema description coverage is only 40%, so the description should compensate, but it only clarifies the outcome values and that the note is optional. The required `runbook` and `lang` parameters are explained nowhere in either the schema or the description, leaving the agent to guess what a runbook identifier is and what language affects.

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

Purpose4/5

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

The description uses a specific verb (record) plus a clearly bounded resource (the current step of a learning path), and enumerates the outcome vocabulary. It is distinguishable from progression-style siblings by stating that it both records the result and advances the learner, though it never names a sibling alternative explicitly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the agent must infer that this is called once per step when a step is finished, skipped, or struggled with. There is no explicit when-not guidance and no mention of alternatives such as next_step, so an agent deciding between advancing and merely viewing must reason it out.

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.