Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

motogp_circuit_poles

Retrieve native MotoGP circuit pole records by result-circuit UUID and category, preserving source row order, rider entries, and pagination metadata for accurate analysis.

Instructions

Get native MotoGP circuit pole records. Preserves every native rider/count row, source ordering and pagination metadata. Uses result-circuit UUIDs and lowercase circuit-statistics categories; no new rank, total or historical category alias is calculated.

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": {
      "circuit_uuid": "<circuit_uuid>",
      "category_name": "<category_name>"
    },
    "name": "motogp_circuit_poles"
  }
}

Input Schema

NameRequiredDescriptionDefault
circuit_uuidYesNative result-circuit UUID from result event metadata
category_nameYesNative circuit-statistics category name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/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 reasonably well: it discloses that every native rider/count row, source ordering, and pagination metadata are preserved, and that no derived rank, total, or historical alias is computed. It omits authentication or rate-limit context, but the core output behavior is clearly communicated.

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?

Three tight sentences, each earning its place, with the purpose front-loaded and constraints following. No filler or repetition.

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?

For a two-parameter read with no output schema or annotations, the definition covers scope, return-shape guarantees, and constraints adequately. It could mention compatibility of the UUID with sibling tools, but nothing essential 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 coverage is 100%, with the enum already listing lowercase category values, so the schema does most of the work. The description reinforces the UUID namespace ('result-circuit') and lowercase categories but adds little syntax or format detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence gives a specific verb and resource: 'Get native MotoGP circuit pole records.' The word 'poles' distinguishes it from siblings like motogp_circuit_wins and motogp_circuit_records, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

The definition implies usage through constraints ('Uses result-circuit UUIDs and lowercase circuit-statistics categories') but never states when to pick this over motogp_circuit_wins or motogp_circuit_records. The 'no new rank, total or historical category alias' caveat is a useful boundary, yet there is no explicit when-to-use or exclusion 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