Skip to main content
Glama

about

Retrieve platform information, pricing details, usage statistics, or documentation for MCP Analytics based on the specified topic.

Instructions

Get platform info, pricing, usage stats, or documentation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesTopic: platform, pricing, current_usage, manual, or a docs section

Implementation Reference

  • src/index.js:43-44 (registration)
    The 'about' tool is registered in the STATIC_TOOLS catalog array with its name, description, and inputSchema.
    const STATIC_TOOLS = [
      { name: "about", description: "Get platform info, pricing, usage stats, or documentation.", inputSchema: { type: "object", properties: { topic: { type: "string", description: "Topic: platform, pricing, current_usage, manual, or a docs section" } }, required: ["topic"] } },
  • The inputSchema for the 'about' tool defines one required 'topic' property (string) describing the topic of interest.
    { name: "about", description: "Get platform info, pricing, usage stats, or documentation.", inputSchema: { type: "object", properties: { topic: { type: "string", description: "Topic: platform, pricing, current_usage, manual, or a docs section" } }, required: ["topic"] } },
  • The 'about' tool's actual execution is proxied to the remote MCP server via remoteClient.callTool(). The generic CallToolRequestSchema handler forwards all tool calls (including 'about') to the remote API.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      if (!remoteClient) {
        return {
          content: [
            {
              type: "text",
              text: "MCP Analytics API key required. Set MCP_ANALYTICS_API_KEY in your environment.\nGet a free key at https://app.mcpanalytics.ai",
            },
          ],
          isError: true,
        };
      }
    
      try {
        const result = await remoteClient.callTool({
          name: request.params.name,
          arguments: request.params.arguments || {},
        });
        return result;
      } catch (err) {
        return {
          content: [{ type: "text", text: `Error: ${err.message}` }],
          isError: true,
        };
      }
    });
Behavior2/5

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

No annotations provided, so description carries full burden. It implies a read operation ('get') but doesn't explicitly state read-only, safety, or side effects. No mention of authentication or rate limits.

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?

Single sentence, front-loaded with all key information. No redundant words. Could be slightly more structured but efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one required parameter and no output schema, the description is moderately complete. It doesn't describe response format or behavior for different topics, which would be helpful.

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 describes the 'topic' parameter similarly. The description adds examples of valid topics (platform, pricing, etc.), which provides some additional context but not extensive meaning beyond the schema.

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 tool retrieves platform info, pricing, usage stats, or documentation. It uses the verb 'get' and specifies the resource (platform info, etc.), distinguishing it from siblings like 'billing' or 'tools_info'.

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 explicit when-to-use or when-not-to-use guidance. While it lists topics, it doesn't explain when to prefer this over siblings like 'tools_schema' or 'reports_list' for similar info retrieval.

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/embeddedlayers/mcp-analytics'

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