Skip to main content
Glama
Sign In
Metrx MCP Server

Metrx MCP Server

by metrxbots
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Report Snapshot

metrx_get_report_snapshot
Read-onlyIdempotent

Fetch a frozen executive-report snapshot using its public share token and return the stored data with snapshot hash and methodology version for integrity verification.

Instructions

Fetch one frozen executive-report snapshot by its public share token (the token IS the capability). Returns the STORED snapshot only — never recomputed — plus its snapshot_hash and methodology_version integrity stamps. Response is envelope-shaped: every numeric leaf is a MeasuredValue {value, ci_low, ci_high, method, data_through}. ci fields are null unless the source payload carries a real confidence interval — never fabricated. Requires an API key with the 'read' scope.

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": {
      "share_token": "<share_token>"
    },
    "name": "metrx_get_report_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
share_tokenYesThe report share token (16–64 lowercase hex chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds genuinely new behavior — the token itself is the capability, the payload is stored and never recomputed, and integrity stamps (snapshot_hash, methodology_version) accompany the result. The required 'read' scope is also disclosed, though the response envelope details overlap with what a return-value description would normally carry.

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?

Front-loaded with purpose and the stored-vs-recomputed guarantee, then moves to return shape and auth. The MeasuredValue leaf enumeration is dense but each clause carries information; the parenthetical 'never fabricated' is the only slightly redundant flourish.

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?

With no output schema, the description takes on the burden of describing the envelope and the MeasuredValue leaf shape, and it does so precisely, including the null-ci rule. Auth requirements and integrity stamps are also covered, so an agent has everything needed to call and interpret this tool.

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 100% and the single parameter is fully documented, so baseline is 3. The description earns an extra point by clarifying the token's security semantics — 'the token IS the capability' — which tells the agent the value is a bearer credential, not a lookup key.

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?

States a specific verb and resource — 'Fetch one frozen executive-report snapshot by its public share token' — and sharpens it with 'STORED snapshot only — never recomputed', which distinguishes it from any live/computed report sibling. It stops short of naming which sibling to use instead, so a 4 rather than a 5.

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?

Usage is implied: you call it when you hold a share token and need the archived, immutable version rather than freshly computed numbers. The 'never recomputed' line functions as an implicit when-not signal, but no alternative tool or explicit selection rule is given.

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

Deploy Server

Other Tools