Skip to main content
Glama

Save result

record_story_result

Save how well the learner knew a story after practising it. rating: 1 = new to me, 2 = hard, 3 = okay, 4 = good, 5 = know it perfectly. Returns the next review date.

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": {
      "story_id": "<story_id>",
      "rating": "<rating>"
    },
    "name": "record_story_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratingYes
secondsNoTime spent, optional.
story_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this is a non-readonly, non-idempotent, non-destructive mutation, so the safety profile is covered. The description adds real value by disclosing the consequence — that a successful call schedules the next review — which tells the agent this write affects future state. It stops short of explaining duplicate-submission behavior or validation failures, which matter 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?

Three short sentences, front-loaded with the action and its usage context, followed by the rating scale and the return value. Nothing is redundant and every sentence earns its place.

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

Completeness4/5

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

For a simple three-parameter mutation with no output schema, the description covers purpose, timing, rating semantics, and the shape of the response ('next review date'). The main remaining gap is error/duplicate behavior for a non-idempotent write, which is a modest omission rather than a blocking one.

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 only 33%, so the description carries weight here, and it does: the full 1-5 rating scale is spelled out with meaning for each value, which is the single most important semantic for this tool. The seconds parameter is documented in the schema itself; story_id is left implicit, which is a minor gap.

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 gives a specific verb and resource: recording how well the learner knew a story after practising it. This clearly separates it from read-only siblings such as get_due_reviews or get_progress, which retrieve rather than record. It does not explicitly name a sibling, but the write-vs-read distinction is unambiguous.

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?

The phrase 'after practising it' implies the correct moment to call it, which is useful context. However, there is no explicit when-not guidance, no mention of whether re-submitting for the same story is legitimate (relevant given idempotentHint=false), and no reference to alternatives.

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.

Resources