worklore

get_story

Read-only

Fetch one worklore story by slug — its full markdown (narrative + the 'Reproduce this' contract your agent would run) WITH its capability disclosure attached (tier + findings), so you see what it can do before applying it. Read the capability first; run check_capability on the live artifacts before executing. After you apply the story to the user's task, call report_reproduction with an honest result to record it.

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

Input Schema

Name	Required	Description	Default
`slug`	Yes	The story slug (from search_stories / a worklore URL).

Output Schema

Name	Required	Description	Default
`slug`	Yes
`title`	No
`checks`	No
`markdown`	No
`has_check`	No
`capability`	No
`visibility`	No
`unavailable`	No
`to_check_only`	No
`visibility_note`	No
`after_you_apply_this`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 15, 2026

addedOutput schema / anyOf

Added value: +[
+  {
+    "properties": {
+      "capability": {
+        "properties": {
+          "tier": {
+            "anyOf": [
+              {
+                "enum": [
+                  "T0",
+                  "T1",
+                  "T2",
+                  "T3",
+                  "T4"
+                ],
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "required": [
+          "tier"
+        ],
+        "type": "object"
+      },
+      "markdown": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "slug",
+      "title",
+      "capability",
+      "markdown"
+    ]
+  },
+  {
+    "properties": {
+      "unavailable": {
+        "enum": [
+          "withdrawn or quarantined — do not execute"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "slug",
+      "unavailable"
+    ]
+  }
+]

addedOutput schema / properties / capability / properties

Added value: +{
+  "tier": {
+    "anyOf": [
+      {
+        "enum": [
+          "T0",
+          "T1",
+          "T2",
+          "T3",
+          "T4"
+        ],
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  }
+}

addedOutput schema / properties / checks / properties / has_problem / minimum
```
Added value: +0
```
addedOutput schema / properties / checks / properties / no_problem / minimum
```
Added value: +0
```
addedOutput schema / properties / has_check / const
```
Added value: +true
```
addedOutput schema / properties / visibility / enum
```
Added value: +[
+  "public",
+  "private"
+]
```

First observedOct 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/not-destructive, so the safety profile is covered. The description adds real context beyond that: the returned markdown includes the 'Reproduce this' contract and an attached capability disclosure (tier + findings), plus the requirement to re-check live artifacts before executing. It doesn't mention pagination or limits, but the added workflow context is genuinely useful.

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?

Front-loaded with verb and resource, then layered with workflow steps. The three sentences are dense but each carries distinct information (what is returned, what to check first, what to report after). Slightly heavy but no filler.

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?

An output schema exists so return-value explanation is not strictly required, yet the description usefully characterizes the payload (markdown + capability disclosure). Combined with the explicit sibling workflow, the agent has enough to call and sequence this tool 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?

Single slug parameter at 100% schema coverage, so the schema already documents source and format. The description repeats only the sourcing hint ('slug'), adding marginal value over the schema. Baseline 3 applies when the schema carries the load.

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 ('Fetch one worklore story by slug') and immediately scopes it against the sibling search_stories by emphasizing the singular, slug-addressed nature. An agent can distinguish it from list/create/edit siblings without opening the schema.

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

Usage Guidelines5/5

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

Names the exact workflow and alternatives: read the capability first, then 'run check_capability on the live artifacts before executing', and finally 'call report_reproduction'. It explicitly routes the agent between this tool and two named siblings with conditions.

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

All worklore tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.