Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

gosugamers_article

Read-only

Returns one GosuGamers news or features article by numeric id (from gosugamers_articles): 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.

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": {
      "id": "<id>"
    },
    "name": "gosugamers_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRequired numeric article id from gosugamers_articles.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the bar is lower. The description adds real context: the returned payload includes the full article body as plain text plus related articles, and unknown ids produce a not-found response rather than an error. No mention of rate limits or payload size, which is the only remaining gap.

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 the verb and resource, and the not-found behavior is a useful trailing note. The long field enumeration in the middle is informative but partially redundant with the existing output schema, costing a bit of tightness.

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?

With one required param, full schema coverage, and annotations, the description covers everything needed to invoke correctly: where the id comes from and what happens on a miss. The enumerated return fields are redundant given the output schema, so it stops short of 5.

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 single `id` parameter is already documented as "Required numeric article id from gosugamers_articles." The description's "numeric id (from gosugamers_articles)" is essentially a restatement, adding no format or edge-case detail beyond the schema. Baseline 3 applies.

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") plus the exact lookup key, and names the sibling gosugamers_articles as the source of that id. An agent can distinguish it from the list/search tools 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 to gosugamers_articles to obtain the id, which establishes the correct call sequence, and notes that an unknown id yields not-found. No explicit exclusion of alternatives, but the "requires an id from the list tool" framing is clear enough in practice.

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

All Crawlora MCP toolsInspect
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