Skip to main content
Glama
RowanErasmus

DailyMed MCP Server

by RowanErasmus

get_mapping_statistics

Retrieve statistics about loaded mapping files to monitor data integration status and verify connections between drug identifiers in the DailyMed database.

Instructions

Get statistics about loaded mapping files

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual implementation of the mapping statistics retrieval logic in the MappingService class.
    getStatistics(): {
      pharmacologicClassMappings: number;
      rxNormMappings: number;
      uniqueSetIds: number;
      uniqueRxCUIs: number;
      uniquePharmacologicClasses: number;
    } {
      let totalPharmaMappings = 0;
      let totalRxNormMappings = 0;
      
      for (const mappings of this.pharmacologicClassMappings.values()) {
        totalPharmaMappings += mappings.length;
      }
      
      for (const mappings of this.rxNormMappings.values()) {
        totalRxNormMappings += mappings.length;
      }
      
      return {
        pharmacologicClassMappings: totalPharmaMappings,
  • The DailyMedClient method that calls the mapping service to get statistics.
    async getMappingStatistics() {
      return this.mappingService.getStatistics();
    }
  • src/tools.ts:494-501 (registration)
    Tool registration for get_mapping_statistics.
    {
      name: "get_mapping_statistics",
      description: "Get statistics about loaded mapping files",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • The index handler where the tool call is dispatched to the client.
    case "get_mapping_statistics":
      const mappingStats = await this.client.getMappingStatistics();
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 the tool retrieves statistics, implying a read-only operation, but doesn't clarify aspects like authentication needs, rate limits, response format, or whether it's safe for frequent use. This leaves significant gaps for a tool with zero 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 no wasted words. It front-loads the core purpose ('Get statistics') and specifies the target ('loaded mapping files'), making it easy to parse and understand quickly.

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 the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'statistics' entail (e.g., counts, types, formats) or how the results are structured, leaving the agent uncertain about the tool's behavior and output. For a tool with no structured support, more detail is needed.

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?

The tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter details, so it appropriately avoids redundancy. A baseline of 4 is applied since no parameters exist, and the description doesn't introduce confusion.

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 action ('Get') and resource ('statistics about loaded mapping files'), making the purpose understandable. However, it doesn't differentiate this tool from its many siblings (e.g., get_all_* tools) that also retrieve data, leaving some ambiguity about when to choose this specific tool.

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. With many sibling tools available (e.g., get_all_*, get_mappings_by_rxcui), the description lacks context about specific use cases, prerequisites, or comparisons, leaving the agent without direction.

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/RowanErasmus/dailymed-mcp-server'

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