Skip to main content
Glama

TG-Market MCP Server

get_endpoint_specification

Read-onlyIdempotent

Get the exact specification, query/body parameters, allowed filter values (such as sort_by), 200 OK JSON response schema, and ready-to-use code snippets (Python, JavaScript, cURL) for any TG-Market API v2 endpoint.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "endpoint_id_or_path": "<endpoint_id_or_path>"
    },
    "name": "get_endpoint_specification"
  }
}

Input Schema

NameRequiredDescriptionDefault
endpoint_id_or_pathYesEndpoint ID (e.g. 'rent_gifts_browse', 'buy_stars', 'rent_create_order') or path (e.g. '/api/v2/rent/gifts').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description earns credit by disclosing return composition beyond the annotations – including a 200 OK JSON response schema and ready-to-use Python/JavaScript/cURL snippets – which matters because no output schema exists. It does not mention rate limits, auth, or error behavior, keeping it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is one dense, front-loaded sentence with no filler, and every listed element (spec, params, filter values, response schema, code snippets) maps to a concrete output the caller can expect. The enumeration is long but each item earns its place; a brief pointer to a discovery sibling would have been the only addition worth the words.

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?

With no output schema and only one well-documented parameter, the description carries the burden of explaining what comes back, and it does so explicitly by naming the response schema and code snippets. An agent knows what it will receive and what to pass in; nothing essential to a correct single-parameter read call is missing.

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?

There is a single required parameter with 100% schema description coverage, including concrete ID and path examples, so the baseline is already 4. The description reinforces that the parameter accepts 'any TG-Market API v2 endpoint' but adds no further syntax or format nuance beyond what the schema already states.

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?

The description uses a specific verb ('Get') with a clear resource ('the exact specification ... for any TG-Market API v2 endpoint') and enumerates the concrete artifacts returned: query/body parameters, allowed filter values, 200 OK JSON schema, and code snippets. This clearly separates it from data-fetching siblings like get_live_prices or get_gift_catalog_and_visuals, though it never contrasts itself with list_api_endpoints, which could plausibly be a discovery step before this one.

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?

Usage is only implied: 'for any TG-Market API v2 endpoint' tells the agent the input domain, but there is no explicit guidance on when to reach for this versus list_api_endpoints, and no stated prerequisite such as knowing the endpoint ID beforehand. The schema example values ('rent_gifts_browse', '/api/v2/rent/gifts') hint at the workflow, but the agent must infer it.

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