Skip to main content
Glama

Platform overview

get_platform_overview
Read-only

Per-platform summary: listing counts, how many are paying distributions, traded volume over 30 and 90 days, and the median last traded price as a share of issue price.

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_platform_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNoLimit to one platform. Omit for all four.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / platform / description
      Added value: +"Limit to one platform. Omit for all four."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds the substantive behavioral detail that has no other home — the exact metric set the summary contains — but says nothing about aggregation semantics, currency, or whether volume/price are time-weighted.

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?

A single dense sentence that front-loads the resource and enumerates the metrics in a compact list; every clause carries information. Slightly list-like phrasing but no wasted words.

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?

With no output schema, the description correctly shoulders the burden of explaining what comes back, which it does at a metric-name level. It stops short on details an agent would want — units (USD?), whether the 30/90-day windows are rolling, and what "median last traded price as share of issue price" is aggregated over.

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% and the enum of four platforms plus the "omit for all four" default is fully documented in the schema. The description adds no meaning beyond that, so the baseline 3 applies.

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?

"Per-platform summary" plus an explicit list of the metrics returned (listing counts, paying distributions, 30/90-day volume, median last traded price as share of issue price) tells an agent precisely what this tool yields, and the platform-level aggregation implicitly separates it from the property-level siblings. It lacks an explicit verb ("returns/computes") and never names a sibling, so it is clear but not fully differentiated.

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 contains no when-to-use or when-not-to-use guidance; the only routing hint ("Omit for all four") lives in the schema, not the description. An agent must infer that this is the right entry point for cross-platform comparison rather than property-level lookups.

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