Skip to main content
Glama

about

Retrieve platform information, pricing details, usage statistics, or documentation for the MCP Analytics server's data analysis and reporting capabilities.

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

  • The tool execution is dynamic: it proxies the tool call (including "about") to a remote server using `remoteClient.callTool`. There is no local hardcoded implementation for "about"; it is retrieved from the remote catalog.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool 'Gets' information implying read-only access, but fails to mention response formats, caching behavior, whether usage stats are real-time, or any rate limits. The behavioral disclosure is minimal.

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 no wasted words. It is appropriately front-loaded with the action verb and immediately lists the resource categories. Every word earns its place.

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?

For a single-parameter tool with 100% schema coverage and no output schema, the description is minimally adequate. However, given the presence of potentially overlapping siblings (billing, tools_info), the lack of differentiation guidance and the absence of any indication of what the tool returns leaves gaps that prevent a higher score.

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%, so the parameter description already documents the valid topics (platform, pricing, current_usage, manual). The description reinforces these concepts by listing them in the main text ('platform info, pricing, usage stats, or documentation'), but does not add syntax details, examples, or semantic nuances beyond what the schema provides. Baseline 3 is appropriate.

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 clear verb ('Get') and lists specific resources (platform info, pricing, usage stats, documentation). It implicitly distinguishes from siblings like 'billing' or 'datasets_read' by focusing on general platform metadata rather than specific operational data, though it lacks explicit contrast with the 'billing' tool which may also handle pricing information.

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?

The description provides no guidance on when to use this tool versus siblings like 'billing' (which may overlap on pricing), 'tools_info', or 'discover_tools'. There are no prerequisites, exclusions, or alternative suggestions provided.

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