Skip to main content
Glama

clearGeoCache

Remove stored geolocation data from the cache to ensure accurate location updates and optimize system performance.

Instructions

Clear the geolocation cache

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the clearGeoCache tool. It calls geoCache.clear() to clear the geolocation cache and returns a confirmation message.
    handler: async () => {
      geoCache.clear();
      return {
        content: [{
          type: 'text',
          text: JSON.stringify({
            message: 'Geolocation cache cleared'
          }, null, 2)
        }]
      };
    }
  • Input schema for the clearGeoCache tool, which requires no parameters.
    inputSchema: {
      type: 'object',
      properties: {}
    },
  • src/index.ts:27-33 (registration)
    Spreads geoTools (which includes clearGeoCache) into the allTools object, which serves as the central registry for all MCP tools used in listing and execution handlers.
    const allTools: ToolKit = {
      ...encodingTools,
      ...geoTools,
      ...generatorTools,
      ...dateTimeTools,
      ...securityTools
    };
Behavior2/5

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

With no annotations, the description carries full burden. It implies a destructive mutation ('clear'), but doesn't disclose behavioral traits like whether this requires permissions, what 'clear' entails (e.g., deletion vs reset), side effects on 'geolocate', or error handling. This is a significant gap for a mutation tool.

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. Every word earns its place without redundancy.

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 tool's complexity (a destructive operation with no annotations or output schema), the description is incomplete. It lacks details on behavior, outcomes, or error cases, leaving the agent under-informed. The conciseness doesn't compensate for these gaps in context.

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 schema description coverage is 100% (empty schema). The description doesn't need to add parameter details, so it meets the baseline of 4 for zero-parameter tools. No additional semantic value is required or provided.

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 'Clear the geolocation cache' clearly states the action (clear) and target resource (geolocation cache). It distinguishes from siblings like 'geolocate' (which likely reads from the cache) by specifying a destructive operation. However, it doesn't explicitly contrast with all siblings, keeping it at 4 rather than 5.

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. The description doesn't mention prerequisites (e.g., after geolocation errors), exclusions, or related tools like 'geolocate' for cache reads. This leaves the agent with minimal context for decision-making.

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

Related 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/MissionSquad/mcp-helper-tools'

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