Skip to main content
Glama

Story sentences

get_story
Read-only

All sentences of one story in the native and the learning language (with transliteration where the script needs it). Use it to practise sentence by sentence.

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>"
    },
    "name": "get_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
story_idYes
max_sentencesNoDefault 60, at most 200.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The description adds useful behavioral detail beyond the readOnlyHint annotation by stating that results include native-language and learning-language sentences with transliteration where needed. However, it does not describe ordering, limits, or how max_sentences affects the returned content.

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?

The description is short, front-loaded with the core return content, and followed by a brief usage note. There is no redundant or filler wording.

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 simple read-only retrieval tool with two parameters and no output schema, the description covers the main return content but leaves gaps around story_id semantics, max_sentences behavior, and the exact shape of the returned sentence data.

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 50%. The description implies that story_id identifies a single story, but it does not explain the parameter further, and it does not mention max_sentences at all. The schema documents max_sentences, but story_id remains largely undocumented in both schema and description.

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 states a specific resource and scope: 'All sentences of one story in the native and the learning language.' This clearly tells the agent it retrieves sentence content for a single story, though it does not explicitly differentiate itself from siblings such as get_daily_stories.

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 'Use it to practise sentence by sentence' gives an implied usage context, but the description does not say when to choose this tool over alternatives like get_daily_stories or when not to use it.

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