Skip to main content
Glama

get_draws

Official China Welfare Lottery double-color-ball draws: up to 400 most recent, plus live SHA-256 beacon. Free data layer.

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": "get_draws"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does disclose useful traits: a hard cap of 400 results, the presence of a live SHA-256 beacon (verifiable fairness), and 'free data layer' implying no auth or cost. However, it says nothing about what the beacon actually is, the return shape, ordering, or what happens when count is omitted or exceeds 400.

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?

One compact sentence with the resource and limit front-loaded; nothing is padded. The trailing 'Free data layer' is a fragment that adds modest value (no auth/cost) but is vague enough to be marginal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter read tool with no output schema, the description covers what is fetched and the size cap. Gaps remain around the default count and the response structure, which an agent would need to construct a correct call and interpret results.

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?

The single 'count' parameter has 0% schema description coverage, so the description must compensate. 'Up to 400 most recent' effectively communicates the upper bound and the ordering (most recent first), but the default when count is omitted and the type (number vs integer) are left unstated.

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?

Names a specific resource (China Welfare Lottery double-color-ball draws) and states what is returned (up to 400 most recent draws plus a live SHA-256 beacon). No sibling overlaps in this catalog, so no differentiation is needed. It stops short of an explicit verb like 'fetch/return', but the resource is unmistakable.

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

Usage Guidelines2/5

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

The description never says when to call this versus anything else, nor any precondition for use. 'Up to 400 most recent' hints at the scope of a valid request, but no usage context or exclusions are given.

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.