Skip to main content
Glama

Corpus state and counts

corpus_state
Read-onlyIdempotent

Use to judge how representative CrawlCheck's public dataset is before quoting its figures. Returns how many distinct domains have been measured, how they split by platform, rendering, size, language and kind, and which strata are still under-sampled. No input; read-only. For CrawlCheck's headline figures use public_counts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/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 description earns credit only for what it adds: the return contents and the fact that under-sampled strata are surfaced, which is genuinely useful framing for judging representativeness. 'No input; read-only' largely restates the annotations, and no detail is given on how strata are defined or how counts are scoped (all-time vs. recent), 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?

Three tight sentences ordered as purpose, then return contents, then sibling routing — the important guidance is front-loaded and nothing is buried. The 'No input; read-only' clause is mild redundancy against the annotations and is the only expendable text.

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 no output schema, the description carries the burden of describing return values, and it does so by naming the dimensions of the breakdown plus the under-sampled-strata signal. What is missing is the concrete shape of the response (top-level fields, whether counts are nested per stratum), which would help an agent parse results, but the framing is sufficient to decide and call it correctly.

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 the baseline is 4. The description correctly reinforces that no input is required, which prevents an agent from probing for optional filters, but there is no further parameter meaning to convey.

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?

The description states a specific verb and resource ('judge how representative CrawlCheck's public dataset is') and enumerates the exact breakdowns returned: distinct domains, platform, rendering, size, language, kind. It also explicitly contrasts itself with the sibling public_counts, so an agent can distinguish the two without opening either 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?

It gives an explicit when ('before quoting its figures') and an explicit alternative with its selecting condition ('For CrawlCheck's headline figures use public_counts'). Both the trigger and the exclusion are stated, leaving nothing 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.