Skip to main content
Glama

list_sentinels

Read-onlyIdempotent

List public Mainnet Sentinels or unfunded practice templates.

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_sentinels"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds useful scope context by noting Mainnet sentinels are public and practice entries are unfunded templates, but it does not state ordering, result volume, or pagination behavior for a list operation.

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 front-loaded sentence with no filler; the two possible result sets are named immediately. Nothing in it could be cut without losing information.

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

Completeness3/5

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

With no output schema and no parameter descriptions, the definition is thin: it does not describe the shape of a returned sentinel record, whether results are paginated or sorted, or the default network. For a simple read-only list tool this is borderline adequate but leaves real gaps.

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 coverage is 0% and only the enum values are self-describing, so the description does carry weight: it explains what each enum value yields (public mainnet sentinels vs unfunded practice templates). It does not state what happens when network is omitted, despite the parameter being optional, leaving the default behavior unstated.

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?

States a specific verb (List) and resource (Sentinels), and distinguishes the two variants it returns: public Mainnet Sentinels versus unfunded practice templates. It does not, however, differentiate itself from the sibling get_sentinel, so an agent must infer that this returns many while get_sentinel returns one.

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?

The mapping of 'public Mainnet Sentinels' to the mainnet case and 'unfunded practice templates' to the practice case implies which network value to choose, but there is no explicit when-to-use or when-not-to-use statement and no mention of get_sentinel as the alternative for a single sentinel.

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.