Skip to main content
Glama
Sign In
gov-gazetteer-mcp

gov-gazetteer-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

cache_status

Read-only

Reports this session's GOV requests by operation and cache usage without making a network call, so you can inspect caching behavior.

Instructions

Report this session's requests to GOV, by operation, and cache use. Makes no network call.

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": "cache_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Goes beyond the annotations by stating that it reports session-scoped, per-operation request counts and cache usage, and explicitly that it makes no network call — corroborating and extending openWorldHint=false. No output schema exists, so the brief sketch of what the report contains is the main behavioral signal; a bit more on timing/scope of the counts would complete it.

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?

Two short sentences, front-loaded with the resource and scope, with the no-network caveat as a second tight clause. Nothing is wasted.

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?

For a parameterless, annotation-covered, read-only diagnostic tool, the description supplies enough to call it correctly and to know roughly what comes back. The absence of an output schema slightly raises the bar, but the mention of per-operation breakdown and cache use covers the essentials.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline applies.

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 specific verb+resource: reports this session's requests to GOV broken down by operation, plus cache use. This clearly separates it from the sibling tools that fetch GOV data (gov_search, gov_object, etc.), though 'GOV' and 'cache use' are left somewhat unexplained.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: this is an introspection/diagnostic tool rather than a data-fetching one, and the 'makes no network call' clause hints at when it is cheap to call. No explicit when-to-use or when-not-to-use guidance or named alternatives are given.

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

Deploy Server

Other Tools