Skip to main content
Glama

ASI.EXPRESS

catalog_stats

Read-onlyIdempotent

Size of the catalog behind search_capabilities: the number of tools (entries_total). Takes no arguments. Call it to see how big the catalog is before relying on a search; the number can be up to an hour old. Read-only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint, destructiveHint, and openWorldHint, so 'Read-only' adds little. The valuable additions beyond annotations are the staleness disclosure ('up to an hour old') and 'Takes no arguments' — the freshness caveat is exactly the kind of trait an agent needs to interpret the number correctly.

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 short sentences, front-loaded with the definition of what the number means, then behavior, then the staleness caveat. The trailing 'Read-only' is redundant with readOnlyHint annotations, a minor bit of unearned wording.

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?

For a zero-argument statistics tool with an output schema already covering return values, nothing is missing: what is measured, the field name, the no-argument nature, and the freshness limit are all stated.

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, so the baseline is 4. The description reinforces this with 'Takes no arguments,' which is consistent with the empty schema and prevents any attempt to pass filters.

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 resource ('Size of the catalog behind search_capabilities') and the exact field returned ('entries_total'), and it positions the tool relative to a named sibling (search_capabilities). An agent can immediately tell this is a catalog-size metric tool rather than a search or lookup tool.

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?

It gives clear when-to-use guidance: 'Call it to see how big the catalog is before relying on a search.' That frames the decision context (sanity-check scale before searching). It stops short of explicit when-not guidance or naming alternatives, so it lands below a 5.

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