Přečíst celý článek
get_articleGet a published article by its slug or exact canonical URL, including the byline, dates, full HTML body and source links.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | ||
| slug | No |
get_articleGet a published article by its slug or exact canonical URL, including the byline, dates, full HTML body and source links.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | ||
| slug | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed world), so the description's job is to add substance — and it does, disclosing that only *published* articles are returned and listing the returned payload (byline, dates, full HTML body, source links). Useful additions would have been what happens for drafts/unpublished slugs and whether the HTML body is ever truncated.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence, front-loaded with the action and identifier modes, then the payload. No filler, nothing that repeats a structured field verbatim.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-record read tool with rich annotations and no output schema, the description is nearly sufficient — it effectively serves as a return-value summary. Remaining gaps (behavior on unpublished/draft identifiers, error semantics on ambiguous URL vs slug) are minor for this level of complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description carries the burden — and it explains both parameters meaningfully: identification by slug or by *exact canonical* URL, which is a real constraint not encoded in the schema's bare string type. It leaves out format specifics (slug shape, whether a trailing slash or tracking params break the URL match) and the length limits that live only in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource ('Get a published article') and enumerates what comes back: byline, dates, full HTML body and source links. It is immediately clear what the tool does. It stops short of naming or contrasting with the sibling search_articles, so it lands at 4 rather than 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied rather than stated: the agent can infer this is the lookup-by-identifier path, and 'exact canonical URL' signals that non-canonical or partial URLs will fail. There is no explicit when-to-use/when-not statement and no pointer to search_articles for cases where only a title or keyword is known.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.