Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gosugamers_article

Retrieve a GosuGamers article by numeric ID, including title, authors, publish times, headline image, full plain text, and related articles.

Instructions

GosuGamers article. Returns one GosuGamers news or features article by numeric id: type, title, teaser, section, publish and update times, headline image with caption, authors, the full text as plain text and related articles. An unknown id returns not found. Take id from gosugamers-articles.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric article id from gosugamers-articles

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it enumerates the returned fields, notes the full text is plain text, and discloses error behavior ('An unknown id returns not found'). It omits any statement about auth, rate limits, or whether the id format is validated, which keeps it below a 5.

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?

One compact paragraph with the operation stated first, then return fields, then error behavior, then the id source. The field enumeration is long but earns its place because there is no output schema.

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?

No output schema exists, so describing the returned fields is necessary and is done thoroughly; error behavior is also covered. The remaining gap is behavioral context beyond return shape (auth, rate limits, freshness), which is minor for a read-by-id 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 the schema property already says 'Numeric article id from gosugamers-articles'; the description repeats essentially the same facts. Baseline 3 for a single fully-documented parameter with no added semantic value.

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 ('Returns one GosuGamers news or features article by numeric id') and scopes it as a single-item fetch, which cleanly separates it from the list-oriented gosugamers_articles sibling. An agent can identify the operation 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 Guidelines4/5

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

Explicitly routes the agent: 'Take `id` from gosugamers-articles', telling it where the required input comes from. It does not state exclusions (e.g. 'do not use for search/keyword lookup'), so it stops short of full when/when-not guidance.

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