Skip to main content
Glama

TG-Market MCP Server

list_api_endpoints

Read-onlyIdempotent

List all 39 official TG-Market REST API v2 endpoints with their exact HTTP methods, paths, categories, and summaries. Filterable by category.

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

Input Schema

NameRequiredDescriptionDefault
categoryNoFilter endpoints by functional category (default: 'all').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds that the set is a fixed catalog of 39 endpoints with exact methods and paths, which hints at result shape and stability, but it says nothing about auth requirements, result size, or format beyond field names.

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 compact sentences with the resource and returned fields front-loaded and the filter capability second. No filler or redundant phrasing.

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?

With no output schema, the description usefully enumerates what each endpoint record contains (methods, paths, categories, summaries). For a static 39-item read-only catalog no pagination or auth discussion is strictly required, though a note on result size or relation to get_endpoint_specification would close the remaining gap.

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?

Schema coverage is 100% and the single category parameter already documents its enum values and default. The description restates the filterable-by-category behavior without adding syntax, defaults, or edge-case meaning beyond what the schema provides, so the baseline of 3 applies.

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 and resource ('List all 39 official TG-Market REST API v2 endpoints') plus the fields returned (HTTP methods, paths, categories, summaries). It does not distinguish itself from the sibling get_endpoint_specification, so an agent cannot tell from the description alone which one gives single-endpoint detail versus the full catalog.

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?

'Filterable by category' implies a discovery/overview use case, and the mention of all 39 endpoints suggests use when a complete catalog is needed. There is no explicit when-to-use versus get_endpoint_specification or when-not guidance, leaving the choice to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources