Skip to main content
Glama

Get Stats

get_stats
Read-onlyIdempotent

Get the number of published pest control companies, places and categories, and when the data last changed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare the safe read-only, idempotent, closed-world profile, so the description's job is to add scope detail — and it does, specifying that counts cover only *published* entries and that a last-changed timestamp is included. That published-only filter is genuinely valuable behavior since there are no parameters to narrow the query. It stops short of explaining how the timestamp is derived or whether counts are cached.

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?

A single sentence that front-loads the three counts and appends the freshness indicator, with no filler or restatement of the title. Every clause contributes information.

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?

With zero parameters and no output schema, the description carries the full burden of describing the return value, and it does list the three counts plus the last-changed field. It could be slightly more complete by stating the return shape or whether the counts are broken down per source/category, but nothing essential for a correct call is missing.

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 no parameters, so there is no parameter meaning to add and the baseline applies. The description correctly spends no words on inputs and instead characterizes the output.

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?

"Get the number of published pest control companies, places and categories, and when the data last changed" names the resource (counts of three specific entity types) and the accompanying timestamp, so the returned content is unmistakable. It does not explicitly contrast itself with the list_*/get_* siblings, but the aggregate nature of the output implicitly separates it from record-returning tools.

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 only implied: the description makes clear this is a summary/count endpoint, so an agent can infer it belongs in orientation or overview steps. There is no explicit when-to-use, no statement of when to prefer it over list_places/list_categories, and no prerequisites or rate-limit notes.

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