Skip to main content
Glama

Populi connection status

populi_status
Read-onlyIdempotent

Displays the connected Populi instance, key sandbox status, and write-access setting; set verify to test credentials with one live request.

Instructions

Shows which Populi instance this server talks to, whether the key is a sandbox key, and whether writes are enabled. Set verify to make one live request that checks the key works.

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

Input Schema

NameRequiredDescriptionDefault
verifyNoMake a live request to check the credentials

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so safety is covered. The description adds real value beyond them by disclosing that `verify` issues one live network request to validate credentials, which hints at latency and possible failure, while the default path is a local/config read. It stops short of saying what a failed verification looks like, keeping it at 4 rather than 5.

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, zero filler, with the tool's reported outputs front-loaded before the optional live-check behavior. Everything in the text earns its place.

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?

For a one-optional-parameter status tool with no output schema, the description adequately enumerates what comes back (instance, sandbox key, writes enabled) and explains the one flag's side effect. Exact return field names and error behavior are unspecified, a minor gap given the tool's simplicity.

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 100% and the single boolean already carries the description 'Make a live request to check the credentials'. The description restates that nearly verbatim, adding only 'checks the key works', so with the schema doing the heavy lifting the baseline 3 applies.

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 ('Shows') and names the exact facts reported: which Populi instance the server targets, whether the key is a sandbox key, and whether writes are enabled. That is enough for an agent to distinguish this diagnostic/config tool from data-access siblings like populi_get or populi_download without opening any schema.

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?

Usage is only implied: an agent can infer this is a pre-flight/configuration check, but the description never says when to call it, when to skip it, or how it relates to siblings such as populi_describe_api. The single explicit directive covers the `verify` parameter ('Set `verify` to make one live request') rather than tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.