Skip to main content
Glama

List the statuses and their counts

list_statuses
Read-onlyIdempotent

List DiscoverIA's six evaluation statuses for scientific claims (and the provisional product statuses) with their definitions and the number of entries in each. A status says where the evaluation stands, not whether the result is true.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of titles, labels and texts: 'fr' (French) or 'en' (English). Default 'en'. Use the user's language.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: it returns six evaluation statuses plus provisional product statuses, includes definitions and entry counts, and clarifies that status describes evaluation stage rather than truth value.

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 sentences, front-loaded with the main action and return contents. The second sentence earns its place by preventing a likely misinterpretation of what 'status' means.

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 read-only, one-optional-parameter listing tool with rich annotations and no output schema, the description is complete enough: it states what is listed, what accompanies each item (definitions and counts), and how to interpret the status values. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the single 'lang' parameter is fully documented in the schema with its enum values and default. The description does not mention the language parameter, so it adds no parameter meaning beyond what the schema already provides.

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 uses a specific verb and resource: 'List DiscoverIA's six evaluation statuses for scientific claims ... with their definitions and the number of entries in each.' It also adds a conceptual distinction — a status indicates evaluation standing, not truth — which further pins down what the tool returns and how it differs from sibling tools like get_announcement or search_announcements.

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?

The description gives clear context for when this tool is appropriate: when an agent needs the set of evaluation statuses, their definitions, and counts. It does not explicitly name exclusions or alternatives, but the sibling tools are unrelated enough that the intended use is unambiguous.

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