Skip to main content
Glama

Public counts

public_counts
Read-onlyIdempotent

Use when you need to quote one of CrawlCheck's figures about itself. Returns them read from the source: sites_measured, domains_in_corpus, crawler_visits (a rolling window), sections, sections_scored, findings_published, guides_published, with an at timestamp. No input; read-only. For dataset coverage by stratum use corpus_state.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/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, so the safety profile is covered; the description does repeat 'read-only' but adds real context by noting values are 'read from the source', flagging that crawler_visits is a rolling window, and noting the accompanying 'at' timestamp. The rolling-window caveat is the kind of temporal behavior the annotations cannot express. It stops short of saying whether values are cached or how fresh they are, which keeps it off a 5.

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, then the return contents, then the sibling routing — a sensible order with no filler sentences. Minor waste in restating 'read-only' (already in annotations) and in the dense field enumeration, but that enumeration is informative rather than padding.

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

Completeness5/5

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

With no output schema, the description carries the burden of describing return values, and it does so by naming every returned field plus the 'at' timestamp. Combined with the zero-parameter schema and full annotation coverage, nothing an agent needs to invoke or interpret this tool 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?

There are zero parameters, which sets the baseline at 4. The description correctly and explicitly confirms 'No input', so the agent knows no arguments are needed; there is nothing further to document.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — returns CrawlCheck's self-reported figures read from the source — and enumerates the exact fields returned (sites_measured, domains_in_corpus, sections_scored, etc.). It also names the sibling it is not for (corpus_state) along with the distinguishing condition ('dataset coverage by stratum'), so an agent can separate the two without opening a schema.

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

Usage Guidelines5/5

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

'Use when you need to quote one of CrawlCheck's figures about itself' gives an explicit trigger condition, and the closing sentence routes the agent to corpus_state for per-stratum dataset coverage. Both the when-to-use and the alternative are stated rather than left to inference.

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.