Skip to main content
Glama

Fetch a DripMetrics metric (paid)

get_metric
Read-only

Paid via x402 (up to $0.25 per request; exact price per metric in list_metrics). Fetches any GET metric by id with query parameters. Without payment this returns the x402 challenge in _meta["x402/error"]; x402-capable clients (e.g. withX402Client) sign it and retry with _meta["x402/payment"] automatically. Invalid requests fail before payment.

Input Schema

NameRequiredDescriptionDefault
idYesMetric id from list_metrics, e.g. "metrics/vpin".
paramsNoQuery parameters, e.g. {"pair": "BTC-USD", "window": "1h"}. See describe_metric.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only provide readOnlyHint=true. Description adds critical context about the x402 payment process, including costs, the challenge/response flow for x402-capable clients, and that invalid requests fail before payment. This goes beyond annotations to explain unusual behavior.

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?

Description is three sentences, all relevant and front-loaded with the key fact that it is paid. Efficient and no wasted words, though could be slightly more concise.

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?

No output schema, so description should hint at return values. It states 'Fetches... metric by id' but does not describe the success response structure. Covers the unique x402 flow well, but omission of success response details leaves a gap for completeness.

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%, so parameters are well-documented. Description adds minimal extra meaning beyond the schema, mentioning query parameters and referencing describe_metric for details. This meets baseline for high coverage but does not significantly enhance understanding.

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?

Clearly states 'Fetches any GET metric by id with query parameters', identifying verb, resource, and method. Distinguishes from siblings like list_metrics (lists all) and describe_metric (describes schema).

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?

Explains the paid mechanism and x402 challenge/response flow, which guides usage. However, does not explicitly state when to use this tool versus alternatives (e.g., describe_metric for parameter details). References describe_metric in params description, but lacks direct when-to-use/not-use guidance.

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