Skip to main content
Glama
Sign In
ironxyz

ironxyz

by ironxyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list-all-endpoints

Read-only

List all API endpoints organized by category to explore the API structure and find endpoints relevant to your goal.

Instructions

Get a comprehensive overview of all available API endpoints organized by category/tag. Use this to explore the API structure and find endpoints related to your goal.

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-all-endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterByTagNoFilter endpoints by tag (e.g., 'Customer', 'Autoramp')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

The description adds that the overview is organized by category/tag, which is beyond the readOnlyHint annotation. However, it does not disclose details like rate limits, response format, or any limitations, which are not needed given the tool's simplicity.

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?

The description is very concise with two short sentences that front-load key information. No unnecessary words or redundancy.

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?

Despite lacking an output schema, the description sufficiently conveys what the tool returns (a structured overview by tag). The tool is simple with one optional parameter, so the description is complete enough for effective use.

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?

The only parameter 'filterByTag' is fully described in the schema (100% coverage). The description does not add additional meaning beyond what the schema already provides, so baseline 3 applies.

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?

The description clearly states it provides a comprehensive overview of all API endpoints organized by tag. It distinguishes itself from siblings like 'get-api-specs' and 'invoke-api-endpoint' by focusing on exploration and categorization.

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

Usage Guidelines4/5

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

The description explicitly advises using this tool to explore the API structure and find endpoints related to a goal. While it does not articulate when not to use it or compare directly with siblings, the usage context is clear.

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