Skip to main content
Glama
Sign In
Hoppscotch Public Docs MCP

Hoppscotch Public Docs MCP

by KidiXDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_endpoints

List Hoppscotch API endpoints by exact text search or list all, with pagination to retrieve complete results.

Instructions

List endpoints using an exact text fragment, or list all with query="". Paginate for all results.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
offsetNo
doc_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose that results are paginated and that pagination is required to see everything, but says nothing about authentication needs, whether results are ordered, or what a page contains (no output schema either).

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 short sentences, front-loaded with the core action and the query-mode distinction; no filler. Every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter tool with no annotations and no output schema, the description covers only query semantics and pagination. The doc_url scoping parameter, limit default, and offset behavior are unexplained, leaving real gaps an agent would guess at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It does explain the query parameter's semantics (exact text fragment; empty string means list all), but limit, offset, and especially the cryptic doc_url are left entirely undocumented in both schema and description.

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 a specific verb (List) and resource (endpoints) and clarifies the two modes: filtered by exact text fragment or unfiltered via query="". It does not explicitly name a sibling like get_endpoint to contrast with, so it falls short of a 5.

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

Usage Guidelines3/5

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

It implies when to use each mode (fragment search vs empty query for all), which is useful context, but gives no explicit exclusions and never mentions the sibling tools (get_endpoint, search_documentation) that an agent must choose between.

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