Skip to main content
Glama

Tell us what data you needed and did not find

request_data

Name the dataset, field, company or analysis you wanted and why. No charge, needs no key, never metered, and read every week: the most-asked-for data is what gets added next. Do not send personal data (emails and phone numbers are removed). GET the same URL for the field list. At most 10 requests per address per day. (POST https://app.deepvalues.ai/api/v1/request-data — no charge; needs no credentials)

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

Input Schema

NameRequiredDescriptionDefault
whyNoThe task you were doing, so we build the right thing.
kindNoWhat sort of gap: a dataset, a field, an analysis, a company we do not cover, a bug.
toolNoThe tool you were using when you hit the gap.
wantYesWhat you wanted, e.g. "Quarterly segment revenue for NVDA".
clientNoYour agent or app name (optional).
tickerNoThe company it was about, if any.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false) by disclosing cost (no charge, no key, never metered), cadence (read every week), a concrete rate limit (10 requests per address per day), and a privacy behavior (emails and phone numbers are removed). These are exactly the operational facts an agent needs before firing a write-shaped call, and they are consistent with the declared hints.

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?

The core instruction and the key constraints are front-loaded in the first two sentences, and nothing is padded. The trailing parenthetical with the literal POST URL is somewhat extraneous for an agent invoking a tool, and the "GET the same URL for the field list" clause is a speed bump in an otherwise tight paragraph.

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 six-parameter, write-shaped tool with no output schema, the definition covers purpose, cost, rate limiting, privacy handling and cadence — a strong package. What it omits is any sense of what a successful submission returns or whether confirmation exists, which matters slightly more given no output schema is supplied.

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 every parameter is already documented in the input schema, and the description's enumeration of "dataset, field, company or analysis" largely mirrors the kind enum rather than adding new meaning. The one mild value-add is direction on why to supply the reason, which is already implied by the schema text. Baseline 3 applies.

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 title and first sentence state a specific verb and resource: name the dataset, field, company or analysis you wanted plus the reason. This unambiguously separates it from data-retrieval siblings such as fundamentals, news or filings — it is a request/feedback channel, not a data source.

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 framing "what data you needed and did not find" plus "the most-asked-for data is what gets added next" makes the triggering condition clear: a gap the caller hit. It does not explicitly say when NOT to use it (e.g. don't file a request for data an existing sibling already returns), and the aside about GETting the same URL for the field list sits ambiguously beside the main instruction.

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