Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pcgamer_sections

Get the eight top-level PC Gamer sections accepted by pcgamer-headlines—deals, games, gaming-industry, guides, hardware, movies-tv, news, and software—with slug, name, and URL.

Instructions

Get PC Gamer sections. Lists the eight top-level PC Gamer sections accepted by pcgamer-headlines: deals, games, gaming-industry, guides, hardware, movies-tv, news and software. Each entry has its slug, display name and url.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior4/5

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

There are no annotations, so the description must carry behavioral context. 'Get' and 'Lists' clearly indicate a read-only lookup, and the description discloses the return shape (slug, name, url) without claiming any mutation. It does not mention auth, rate limits, or explicit safety guarantees, but for a zero-parameter discovery tool this is largely sufficient.

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

Conciseness5/5

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

The definition is front-loaded with the core action ('Get PC Gamer sections') and then supplies only the useful details: the exact section slugs and returned fields. Every sentence earns its place, with no filler.

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?

Given the low complexity, empty input schema, no output schema, and no annotations, the description is complete enough: it names the resource, the exact section values, and the fields returned in each entry. Nothing essential for calling this tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so there are no parameter semantics to document. The baseline for a no-parameter tool is 4, and the description appropriately does not invent or detail any input arguments.

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 ('Get PC Gamer sections') and immediately distinguishes itself by naming the eight top-level section slugs accepted by `pcgamer-headlines`. It also specifies the output fields, so an agent can identify this as a section-lookup tool without opening an empty 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?

The description ties the tool to `pcgamer-headlines` by saying the sections are accepted there, which implies the primary use case: discovering valid section slugs before requesting headlines. It does not explicitly say when not to use it or list a sibling alternative, so it falls just short of full routing 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