Skip to main content
Glama

Request data that is not covered yet

request_data

Request data that these tools do not provide yet (another chain, a dataset, a field or a filter), so the maintainers can consider it for a future release. Free. Describe the data and, optionally, the task it is for. Do not include personal information. Requests are stored anonymously and read by the maintainers; the result is only a confirmation.

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": {
      "request": "<request>"
    },
    "name": "request_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesThe data you need, e.g. 'unlock schedule for token X' or 'Ethereum validator stats'
use_caseNoOptional: the task you need it for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / request / description
      Previous value: -"The data you need, e.g. 'token unlock schedules' or 'Ethereum validator stats'"New value: +"The data you need, e.g. 'unlock schedule for token X' or 'Ethereum validator stats'"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations mark this as a non-read-only submission, and the description goes well beyond them: it says the request is free, stored anonymously, read by maintainers, and that the result is only a confirmation. It also warns against including personal information. Missing are rate limits or whether duplicate requests are merged, but the core behavioral picture is unusually complete.

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?

Three short sentences, front-loaded with the purpose and the scope of what may be requested. Every sentence adds a distinct fact (scope, privacy constraint, storage and response behavior) 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?

For a two-parameter submission tool with no output schema, the description covers everything an agent needs: what to send, what not to send, who reads it, and that the return is only a confirmation. No important gap remains.

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%, so the schema already defines both fields and their optionality. The description restates the split ('describe the data and, optionally, the task') and adds one genuine constraint ('Do not include personal information'), but contributes little beyond the structured fields.

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 ('Request data') plus the exact scope ('another chain, a dataset, a field or a filter') and the outcome ('so the maintainers can consider it for a future release'). This clearly separates it from the sibling read-only data tools, which return existing data rather than soliciting new data.

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?

Explicitly conditions use on the data not being provided by 'these tools', which is the decisive selector against the siblings. It does not name any specific sibling or state an explicit when-not beyond that implicit coverage check, so it falls just short of a 5.

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