Skip to main content
Glama
Sign In
PulseNetwork MCP

PulseNetwork MCP

by GTCC777
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

pulse_discover

Read-only

Discover API endpoints across 74 verticals with prices, parameters, and descriptions, so you can choose the cheapest option before calling.

Instructions

FREE — search the PulseNetwork catalog (74 verticals, ~900 endpoints). Returns matching endpoints with price, params, and description. Always discover before calling; prefer the cheapest endpoint that answers the question.

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": "pulse_discover"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 20)
queryNoKeywords, e.g. "flight compensation", "token safety", "clinical trials"
verticalNoRestrict to one vertical id, e.g. "cryptopulse"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark readOnlyHint=true, and the description adds useful context: tool is FREE, catalog size (74 verticals, ~900 endpoints), and the result includes price and parameters. It doesn't contradict annotations; adds value without needing to cover side effects.

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?

Two sentences, front-loaded with 'FREE' and the search verb. No wasted words; every clause adds value (catalog size, return fields, usage priority).

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?

Despite no output schema, the description states what is returned (endpoints with price, params, description) and gives usage direction. With 3 optional params all documented in schema, this is complete for a discovery tool.

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?

Input schema has 100% coverage for all three parameters (limit, query, vertical) with descriptions. The tool description offers no additional parameter-specific semantics, so baseline 3 is appropriate.

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?

Description clearly states it searches the PulseNetwork catalog and returns matching endpoints with price, params, and description. 'Always discover before calling' positions it as the discovery tool distinct from pulse_call and siblings.

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 instructs to 'Always discover before calling', establishing the tool as the mandatory first step, and adds a decision rule to 'prefer the cheapest endpoint' – clear when-to-use guidance versus other tools.

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