Skip to main content
Glama

Ask for an update

request_update

Ask Ultrapedia to research a race again. Use it when something looks out of date, wrong or missing and you do not have a page and quote for propose_correction. issue is outdated (the date, price or start time is of a past edition, or the race has changed), incorrect (a value looks wrong) or missing (the race publishes values that are empty here). fields is a list of the column names you mean; leave it out for the race-day values. note says what you saw. This changes no value: a research agent checks the race's own site, usually within a few days, and the races asked for most are done first.

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": {
      "slug": "<slug>"
    },
    "name": "request_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
slugYes
issueNooutdated
fieldsNo
source_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true and destructiveHint=false, and the description adds genuine context beyond them: 'This changes no value', a human/agent researcher checks the race's own external site, turnaround is a few days, and popular races are queued first. The only gap is what the call itself returns, which is not stated.

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?

Purpose and alternative are front-loaded, and every sentence carries information the agent needs (routing rule, issue vocabulary, field semantics, non-mutation, latency). The prose is dense and slightly run-on, but nothing is padding.

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 five-parameter, non-destructive-but-stateful request tool with no output schema and no documented parameter descriptions, the definition covers the important unknowns: side effects, who does the work, timing, and queue priority. The unmentioned `source_url` parameter is the main incompleteness.

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?

Schema coverage is 0%, so the description must carry the parameter burden, and it does for three of five: it enumerates the legal `issue` values with their meanings, explains `fields` as column names with a default of race-day values, and explains `note` as what you observed. `slug` is left implicit and `source_url` is never mentioned, leaving one parameter entirely undocumented.

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?

The description opens with a concrete verb and object: 'Ask Ultrapedia to research a race again.' It immediately distinguishes this from the closest sibling by requiring that you lack 'a page and quote for propose_correction', so an agent can route between the two without opening either schema.

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?

It names the triggering condition ('something looks out of date, wrong or missing'), the prerequisite that selects this tool over propose_correction, and the issue categories that scope the request. It also sets expectations for what happens after the call ('usually within a few days', prioritization by demand), which is guidance an agent needs to plan.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources