Skip to main content
Glama

What agents looked for around your MCP server (7Maps)

my_server_report
Read-onlyIdempotent

Use this when the person you work for owns an MCP server on the 7Maps map and wants to know how AI agents look for servers like it: requests in its category (7 or 30 days), how often it was shown and picked, and, with owner_key, the words agents used, servers picked instead, reported failures, uptime and its token cost against similar servers. Counts only, no agent identities. Read-only; never changes ranking. No charge.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "server": "<server>"
    },
    "name": "my_server_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoWindow in days: 7 (default) or 30
serverYesThe MCP server address as it appears on its 7Maps page, or its official registry name
owner_keyNoThe owner key returned to the verified owner by claim_mcp_server (the newest one; each verification issues a new key)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / owner_key / description
      Previous value: -"The owner key returned to the verified owner by claim_mcp_server"New value: +"The owner key returned to the verified owner by claim_mcp_server (the newest one; each verification issues a new key)"
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, yet the description still adds real behavioral context: aggregates are counts only with no agent identities, the call never affects ranking, and there is no charge. The owner_key gate (unlocking words used, competing picks, failures, uptime, token cost) is genuine behavior beyond the schema. Slightly dense phrasing costs it a point.

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?

Front-loaded with the trigger condition and tight overall for the amount of information conveyed; no filler sentences. It is a single long comma-chained sentence, so the metric list is harder to scan than a short bulleted structure would be.

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?

There is no output schema, so the description must carry the return shape, and it does by naming the reported metrics and their units (days, counts, comparisons to similar servers). Privacy, billing and side-effect expectations are all covered. It leaves the shape of the metric payload itself somewhat vague (no mention of formatting, pagination or empty-data cases).

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 schema already documents server, days (7/30) and owner_key with its claim_mcp_server provenance. The description adds functional meaning for owner_key by listing which metrics it unlocks, which the schema does not say. It adds nothing about the server parameter's format beyond what the schema states, so the baseline holds.

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?

States a concrete verb and resource: reports how AI agents discover a specific MCP server on 7Maps, enumerating the returned metrics (category requests over 7/30 days, impressions, picks, and owner-only fields). The conditional subject ('the person you work for owns an MCP server') narrows scope well. It never names a sibling such as my_7maps_usage, so the boundary with that tool must be inferred.

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?

Opens with an explicit trigger condition ('Use this when the person you work for owns an MCP server...') and describes the intent that selects it. It also signals a sub-mode gated by owner_key. It does not state when NOT to use it or point to the alternative for account-level usage.

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