Skip to main content
Glama
buildwithgrove

Grove's MCP Server for Pocket Network

get_endpoint_details

Retrieve detailed information about a specific blockchain endpoint, including configuration and capabilities, to verify compatibility and access parameters for blockchain data queries.

Instructions

Get detailed information about a specific endpoint

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endpointIdYesThe ID of the endpoint to retrieve

Implementation Reference

  • Executes the get_endpoint_details tool by retrieving the endpoint configuration using endpointManager.getEndpointById and returning its JSON representation or an error if not found.
    case 'get_endpoint_details': {
      const endpointId = args?.endpointId as string;
      const endpoint = endpointManager.getEndpointById(endpointId);
    
      if (!endpoint) {
        return {
          content: [
            {
              type: 'text',
              text: `Endpoint not found: ${endpointId}`,
            },
          ],
          isError: true,
        };
      }
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(endpoint, null, 2),
          },
        ],
      };
    }
  • Defines the input schema for the get_endpoint_details tool, requiring an endpointId string parameter.
    {
      name: 'get_endpoint_details',
      description: 'Get detailed information about a specific endpoint',
      inputSchema: {
        type: 'object',
        properties: {
          endpointId: {
            type: 'string',
            description: 'The ID of the endpoint to retrieve',
          },
        },
        required: ['endpointId'],
      },
    },
  • src/index.ts:88-101 (registration)
    Registers the endpoint tools, including get_endpoint_details, by calling registerEndpointHandlers and including in the tools list served by ListToolsRequestHandler.
    const tools: Tool[] = [
      ...registerBlockchainHandlers(server, blockchainService),
      ...registerDomainHandlers(server, domainResolver),
      ...registerTransactionHandlers(server, advancedBlockchain),
      ...registerTokenHandlers(server, advancedBlockchain),
      ...registerMultichainHandlers(server, advancedBlockchain),
      ...registerContractHandlers(server, advancedBlockchain),
      ...registerUtilityHandlers(server, advancedBlockchain),
      ...registerEndpointHandlers(server, endpointManager),
      ...registerSolanaHandlers(server, solanaService),
      ...registerCosmosHandlers(server, cosmosService),
      ...registerSuiHandlers(server, suiService),
      ...registerDocsHandlers(server, docsManager),
    ];
  • src/index.ts:122-122 (registration)
    Dispatches tool execution to handleEndpointTool, which contains the logic for get_endpoint_details.
    (await handleEndpointTool(name, args, endpointManager)) ||
  • Helper method used by the tool handler to retrieve an endpoint configuration by its ID from the config.
    getEndpointById(id: string): EndpointConfig | undefined {
      return this.config.endpoints.find(ep => ep.id === id);
    }
Behavior2/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 of behavioral disclosure. It states it 'gets' information, implying a read-only operation, but doesn't specify permissions, rate limits, error handling, or what 'detailed information' entails (e.g., format, fields). This is a significant gap for a tool with no annotation coverage.

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 a single, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly without unnecessary elaboration.

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?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what 'detailed information' includes, potential errors, or behavioral traits like authentication needs. For a tool in a complex blockchain context with many siblings, this leaves critical gaps for an agent to use it effectively.

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 description coverage is 100%, with the parameter 'endpointId' fully documented in the schema. The description adds no additional meaning beyond implying retrieval for a 'specific endpoint', which aligns with the schema. Baseline 3 is appropriate as the schema handles parameter documentation adequately.

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 clearly states the verb ('Get') and resource ('detailed information about a specific endpoint'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_endpoint_docs' or 'list_endpoints', which might retrieve different types of endpoint information or lists.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'get_endpoint_docs' or 'list_endpoints'. The description implies usage for a specific endpoint ID, but lacks explicit context or exclusions, leaving the agent to infer based on tool names alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/buildwithgrove/mcp-pocket'

If you have feedback or need assistance with the MCP directory API, please join our Discord server