Skip to main content
Glama
Sign In

Machinepulse

by tech.machinepulse
OverviewDiscussionsAdmin

Get Market Overview

get_market_overview
Read-onlyIdempotent

Fetch the observatory front page in one call — MCP servers, A2A agents, HF models, x402 money, top-5 growth with one catalog line each, new arrivals per category and data coverage, a few headline numbers each. Read-only aggregation of daily-collected observatory data; no side effects; money figures carry their stated data lag. Use when the user wants the state of the whole market in a single request; for per-metric values with formulas use get_pulse.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond those annotations: daily-collected aggregation and a stated data lag for money figures, though 'read-only' and 'no side effects' partially repeat the annotation hints.

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?

Front-loads the main action and return contents, then follows with read-only/data-lag context and the usage alternative. Despite the enumeration, every clause serves to specify the aggregation or route the agent away from get_pulse.

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?

Given zero parameters, an output schema, and rich annotations, the description is complete enough: it names what is aggregated, notes data freshness caveats, and routes to the correct alternative when the user needs granular metrics. Return-value details can safely live in the output schema.

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 has zero parameters, so parameter semantics baseline is 4. The description correctly presents this as a single-call aggregation with no parameter-specific behavior required.

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 and resource ('Fetch the observatory front page') and enumerates exactly what the response contains across MCP servers, A2A agents, HF models, x402 money, growth, arrivals, and coverage. It clearly distinguishes itself from the sibling tool get_pulse by naming the alternative for per-metric/formula requests.

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?

Explicitly says to use this when the user wants the whole market state in one request, and names get_pulse as the alternative for per-metric values with formulas. The when/when-not routing is direct and leaves little to inference.

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

All Machinepulse toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources