Skip to main content
Glama

My 7Maps usage (personal key)

my_7maps_usage
Read-onlyIdempotent

Use this when the person you work for asks what 7Maps has done for them: calls made with their personal 7Maps key today, in the last 7 days and in the last 30 days, servers checked, an estimate of the tokens saved compared with finding the same thing out without 7Maps, failures avoided (servers not answering that were skipped, risk changes caught by watch or verify_lock, calls that would have failed) and the average response time. It reads the optional personal key sent with this connection (the X-7Maps-Key header); without one it says so in one line, since every 7Maps answer already states its own saving. Only that person's own counts. No charge.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "my_7maps_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
windowNoWhich window to lead with: day (today), week (last 7 days) or month (last 30 days); all three are returned
last_tripNoOptional: {server, tool, ok, ms} of your previous MCP server call

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / last_trip
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Optional: {server, tool, ok, ms} of your previous MCP server call",
      +  "properties": {},
      +  "type": "object"
      +}
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful behavior beyond that: it reads the optional X-7Maps-Key header, returns a one-line notice when absent, reports only that person's counts, and notes there is no charge.

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?

The description is front-loaded around the usage scenario and then lists the returned metrics. It is dense and slightly run-on with parentheticals, but most of the detail is relevant to an agent deciding whether to call it.

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

Completeness4/5

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

Given the read-only annotations, rich schema descriptions, and lack of an output schema, the description is largely complete: it explains scope, key behavior, and the kinds of metrics returned. It stops short of describing the optional last_trip parameter or the exact response structure, so it is not fully exhaustive.

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%, so the parameters are already well documented. The description reinforces the three time windows and says all three are returned, but it does not mention the optional last_trip parameter, so it adds little 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 a specific reporting purpose: usage for the person's personal 7Maps key, including calls, servers checked, token savings, failures avoided, and response time. It is distinguishable by its personal-key scope, though it does not explicitly contrast itself with nearby siblings such as my_server_report.

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

Usage Guidelines4/5

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

It gives a concrete trigger: use when the person asks what 7Maps has done for them. It also explains the no-key case, but it does not name alternatives or explicitly state when not to use this tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources