MoveSurge

Read an explainer article

get_article

Read-only

Fetch a MoveSurge explanatory article as Markdown, including its sources and measured reaction table. Call with no slug to list the 25 most recent articles.

Input Schema

Name	Required	Description	Default
`slug`	No	Article slug; omit to list recent articles.

Output Schema

Name	Required	Description
`url`	No
`slug`	No
`error`	No
`title`	No
`articles`	No	Returned instead of one article when no slug is given.
`markdown`	No
`as_of_utc`	No
`data_note`	No
`data_status`	No
`withheld_rows`	No
`returned_counts`	No
`newest_result_utc`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026
- addedOutput schema / properties / withheld_rows
```
Added value: +{
+  "type": "object"
+}
```
Changed6 schema fields changedOct 18, 2026
- addedOutput schema / properties / articles / items / properties / url
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```
- addedOutput schema / properties / as_of_utc
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data_note
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data_status
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / newest_result_utc
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / returned_counts
```
Added value: +{
+  "type": "object"
+}
```
First observedOct 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: results are Markdown and include sources and a measured reaction table, and the slugless mode returns a capped list of 25 recent articles.

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 tight sentences, no filler. The primary fetch behavior is front-loaded and the alternate listing mode follows immediately.

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?

An output schema exists, so return-value structure need not be repeated, and the description still supplies the output format and content highlights. Both invocation modes are covered and no prerequisites or gotchas are left implicit.

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 100% and the schema already states that omitting slug lists recent articles. The description adds meaning by quantifying that list ('the 25 most recent articles') and implying the slug selects a specific article, which is slightly more than the schema provides.

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?

The description states a specific verb ('Fetch') and resource ('a MoveSurge explanatory article') plus the output format (Markdown) and the notable contents (sources, measured reaction table). It also documents the second mode (listing with no slug), making it fully distinguishable from siblings like explained_moves or search_headlines.

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?

It clearly explains the conditional invocation: call with no slug to list the 25 most recent articles. There is no explicit when-not-to-use or named alternative, but the sibling set contains no competing article fetcher, so the context is unambiguous.

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

All MoveSurge 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.

Resources

Need Help?