market-pulse

Grading methodology

pulse_methodology

Read-onlyIdempotent

Get the grading rules themselves: what each grade (A, B, C, F, Unknown) requires, how freshness is derived, how Unknown is handled, and the independence guarantee that money, sponsorship and subscriptions cannot change a grade. Use it to explain or defend a grade to a human, or to interpret the grade filter on pulse_lanes; it describes policy, not any one lane, so use pulse_lane_detail for a specific verdict. Takes no arguments, read-only and idempotent. Works without an API key on the free tier. Returns {version, grades, rules[], independence, snapshotAt, dataset}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`rules`	Yes	The grading rules in order of precedence.
`grades`	Yes	Label for each grade.
`version`	Yes	Methodology version.
`independence`	Yes	The independence guarantee.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "grades": {
+      "additionalProperties": true,
+      "description": "Label for each grade.",
+      "type": "object"
+    },
+    "independence": {
+      "description": "The independence guarantee.",
+      "type": "string"
+    },
+    "rules": {
+      "description": "The grading rules in order of precedence.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "version": {
+      "description": "Methodology version.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "version",
+    "grades",
+    "rules",
+    "independence"
+  ],
+  "type": "object"
+}

First observedSep 30, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, but the description adds context the annotations cannot: no arguments required, and it works without an API key on the free tier, which matters for an agent deciding whether the call is viable. It also sketches the response shape, though that partially duplicates the output schema.

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 content, then routing, then operational notes. Efficient overall, though the enumerated return-shape clause duplicates the existing output schema and 'read-only and idempotent' restates annotations.

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?

An output schema exists, so return values need not be explained, and the description still names the key fields. Combined with the routing guidance and free-tier note, an agent has everything needed to select and invoke this tool correctly.

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?

Zero parameters, so the baseline is 4; the description confirms 'takes no arguments', removing any ambiguity about whether inputs are expected. Nothing more can be added for a parameterless tool.

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?

States a specific verb+resource ('Get the grading rules themselves') and enumerates the content precisely: grade requirements for A/B/C/F/Unknown, freshness derivation, Unknown handling, and the independence guarantee. It also explicitly names the sibling it is not (pulse_lane_detail), so an agent can separate the policy tool from the per-lane verdict tool without reading either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives both sides of the routing decision: use it to explain or defend a grade to a human, or to interpret the grade filter on pulse_lanes; use pulse_lane_detail instead for a specific verdict. The condition selecting the alternative is named, not implied.

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

All market-pulse 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.