mcp

Global market aggregates

get_global_market

Read-only

Global market aggregates: BTC dominance, total market cap, total volume.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`data`	Yes
`meta`	No	Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 7, 2026

addedOutput schema / properties / data / additionalProperties
```
Added value: +{}
```

addedOutput schema / properties / data / properties

Added value: +{
+  "marketCapPercentage": {
+    "anyOf": [
+      {
+        "additionalProperties": {},
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "totalMarketCap": {
+    "anyOf": [
+      {
+        "additionalProperties": {},
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "totalMarketVolume": {
+    "anyOf": [
+      {
+        "additionalProperties": {},
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  }
+}

addedOutput schema / properties / data / type
```
Added value: +"object"
```
removedOutput schema / properties / error
```
Removed value: -{}
```

addedOutput schema / properties / meta / description

Added value: +"Envelope metadata. Carries `_truncated` when a list was abridged to fit the response budget."

addedOutput schema / required
```
Added value: +[
+  "data"
+]
```

Changed2 schema fields changedAug 19, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedAug 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only the content of the aggregates; it says nothing about freshness, caching, rate limits, or whether the snapshot is point-in-time versus rolling, so it clears the lowered bar without adding much.

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?

A single front-loaded sentence with no filler; the resource leads and the three returned metrics follow immediately. Nothing could be cut without losing information.

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?

With no parameters and an output schema present, the description need not explain return shape, and it correctly names the fields an agent would care about. The only missing piece is routing guidance relative to the many overlapping market-level siblings.

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?

The tool takes zero parameters, so per the baseline rubric there is nothing for the description to disambiguate and a 4 is appropriate. The enumerated metric names are a small bonus for interpreting the empty input surface.

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 the resource (global market aggregates) and enumerates exactly the three metrics returned – BTC dominance, total market cap, total volume – which an agent can distinguish from siblings like get_market_health or get_regime. It lacks an explicit verb and never names a sibling it is not, so it stops short of the top mark.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives in a crowded market-data family (get_market_health, get_market_crossing, get_market_sentiment, get_regime). The agent must infer the use case purely from the metric list.

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

All mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.