Déstaire

Get an article

get_article

Read-onlyIdempotent

One article: its opening paragraphs, or with detail "full" its whole text with every list of places.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	The article's slug, the last part of its URL.
`detail`	No	"concise" (the default): the start of the answer and a count, to save context; "full": all of it.	concise

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`note`	No
`text`	Yes
`photo`	Yes
`title`	Yes
`author`	Yes
`category`	Yes
`published`	Yes
`truncated`	Yes
`standfirst`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```

Changed4 schema fields changedSep 24, 2026

addedInput schema / properties / detail

Added value: +{
+  "default": "concise",
+  "description": "\"concise\" (the default): the start of the answer and a count, to save context; \"full\": all of it.",
+  "enum": [
+    "concise",
+    "full"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / note
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / truncated
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "title",
-  "url",
-  "standfirst",
-  "author",
-  "category",
-  "published",
-  "photo",
-  "text"
-]New value: +[
+  "title",
+  "url",
+  "standfirst",
+  "author",
+  "category",
+  "published",
+  "photo",
+  "text",
+  "truncated"
+]

First observedSep 24, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is fully covered. The description adds that the response body varies by detail level, including place lists at 'full', but it doesn't disclose anything about error behavior for unknown slugs or payload size.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence, so it is not verbose, but the 'One article:' fragment front-loads a noun rather than the action, and the trailing phrase 'with every list of places' is grammatically loose and slightly ambiguous.

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?

With an output schema present and annotations covering safety, the definition's scope is mostly adequate. It still leaves the agent without guidance on tool selection (this tool vs. the list/search siblings) or failure modes, which is a meaningful gap for a lookup tool.

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 description coverage is 100% and both parameters (slug pattern/meaning, detail enum with default) are documented there. The description's nod to detail='full' merely restates the enum, adding no new semantics such as expected text length or cost.

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 names a single-article retrieval and its returned content ('opening paragraphs' vs 'whole text with every list of places'), which separates it from sibling list_articles. The verb is only implied ('Get' comes from the name/title), and the telegraphic 'One article:' opener is less crisp than a full sentence.

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

Usage Guidelines2/5

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

It never states when to pick this tool over list_articles, get_guide, or search_stays, nor what prerequisites (a valid slug) exist. The only usage-adjacent content is the detail tradeoff, which is already carried by the schema.

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

All Déstaire 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?