Skip to main content
Glama
Sign In
Gameball MCP Server

Gameball MCP Server

by Ahmedelmonady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Docs: Get API Endpoint

docs-get-api-endpoint

Retrieve complete details for a REST API endpoint: parameters, request/response schemas, and a cURL example. Use after a topic lookup to get the endpoint-specific information you need.

Instructions

Get full details of a specific REST API endpoint including parameters, request/response schemas, and a cURL example. Use after docs-lookup-topic when you need details on a specific endpoint.

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": "docs-get-api-endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodNoHTTP method: GET, POST, PUT, DELETE
searchNoSearch by keyword in endpoint summaries
endpointNoAPI path, e.g. "/api/v4.0/integrations/transactions/hold"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states what the tool returns (details including schemas and example) and implies a read-only lookup, but it does not disclose any potential side effects, authentication requirements, or error handling. This is adequate for a simple documentation tool but not highly transparent.

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 two sentences, front-loaded with the main purpose and followed by a usage note. There is no redundant information; every word earns its place.

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 having no output schema, the description lists the key contents of the response (parameters, schemas, cURL example). It also provides sequencing with docs-lookup-topic. However, it does not explain how the three optional parameters should be combined to identify a specific endpoint, which would improve completeness.

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?

All three parameters have descriptions in the schema (100% coverage), so the schema already documents their semantics. The description does not add any additional parameter meaning beyond what the schema provides, matching the baseline for high schema coverage.

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 the tool's function: 'Get full details of a specific REST API endpoint including parameters, request/response schemas, and a cURL example.' This uses a specific verb and resource and distinguishes it from sibling tools by noting it should be used after docs-lookup-topic.

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 provides clear context: 'Use after docs-lookup-topic when you need details on a specific endpoint.' This tells the agent when to use the tool, but it does not explicitly mention alternatives or when not to use it, so it falls short of a 5.

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