Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

gosugamers_articles

Read-only

Returns pages of the GosuGamers news and features archive (51,051 articles), newest first, with optional section (dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire, battlegrounds-mobile-india, entertainment, genshin-impact, honkai-star-rail, zenless-zone-zero, honor-of-kings or umamusume-pretty-derby) and type (news or features) filters: id, title, teaser, section, publish time, author, image and URL. page and page_size (up to 100) page through total_rows. Use gosugamers_article with a returned id for the text.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gosugamers_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOptional 1-based page, default 1.
typeNoOptional article type: news or features. Omit for both.
sectionNoOptional section: dota2, counterstrike, lol, valorant, mobile-legends, pubg-mobile, wild-rift, free-fire, battlegrounds-mobile-india, entertainment, genshin-impact, honkai-star-rail, zenless-zone-zero, honor-of-kings or umamusume-pretty-derby. Omit for all sections.
page_sizeNoOptional page size 1 to 100, default 10.

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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the bar is lower, yet the description adds real behavioral context: newest-first ordering, that results page through a total_rows count, and the exact result shape (id, title, teaser, section, publish time, author, image, URL). It stops short of noting rate limits or whether the archive updates live.

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 action and dataset scope, and ends with the essential routing hint. The long duplicated section enumeration is the one inefficiency, since the identical list already lives in the schema, but the rest of the text is dense and waste-free.

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?

For a 4-param, zero-required paging endpoint with full schema coverage and an output schema, the description supplies everything an agent needs: ordering, filter axes, pagination mechanics, returned fields, and the next-step sibling. Nothing necessary for correct invocation is missing.

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 section and type are fully enumerated in the schema, so the description's restatement of the section list adds no new meaning. It does add that page/page_size page through total_rows and that page_size caps at 100, which is the only genuine value add over the schema.

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 pages of the GosuGamers news and features archive), plus scope details (51,051 articles, newest first) and the exact fields returned. It explicitly distinguishes itself from the sibling gosugamers_article, which only fetches full text by id.

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

Usage Guidelines5/5

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

Names the alternative explicitly: 'Use gosugamers_article with a returned id for the text.' The condition that selects each tool (browse/list vs. read one article) is stated directly, and the optional filter semantics ('Omit for both' implied via type) are clear.

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