Skip to main content
Glama
Sign In
geolens-mcp

geolens-mcp

Official
by geolens-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_story

Retrieve a published story's title, summary, visibility, and chapter document by story ID; draft content is excluded and unreadable stories return 404.

Instructions

Get one story's published version: title, summary, visibility and the document with its chapters. Each chapter has a title, blocks and a scene (map_id, camera, layer_visibility); a chapter on a map you can't read comes back without its scene and with scene_hidden true. Never returns the draft. document is null until the story is published, and a story you can't read answers 404.

Args: story_id: Story id (e.g. from list_stories).

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.30.1

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it discloses key behaviors: draft is never returned, document is null until publication, unreadable stories return 404, and unreadable maps yield scene_hidden true with no scene. It does not discuss caching, rate limits, or pagination, but the failure and visibility semantics are unusually well covered.

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?

The main narrative is front-loaded and dense with useful payload information, and the Args section is compact. Minor redundancy in the chapter/block/scene enumeration, but nearly every sentence conveys return-shape or failure semantics.

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 single-parameter read tool with no annotations and no output schema, the description supplies the full response shape (document, chapters, blocks, scene fields) plus visibility, 404, scene_hidden, and null-document edge cases. An agent can invoke and interpret results correctly from this text alone.

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 coverage is 0% and there is one required string parameter; the description says 'story_id: Story id (e.g. from list_stories)', which gives the identifier's source but no format guidance (UUID vs. slug). That is modest value beyond the bare schema, so middle of the range.

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 ('Get one story's published version') and enumerates returned fields (title, summary, visibility, document with chapters, blocks, scene). It also distinguishes itself by noting it never returns the draft, so an agent can tell it apart from list/search siblings.

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?

Implies when to use via the 'published version' and 'Never returns the draft' framing, and references list_stories as the source of story_id. It does not explicitly state when to prefer this over other retrieval paths, but the published-only scope gives clear selection context.

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

Deploy Server

Other Tools