Skip to main content
Glama

Server info

server_info
Read-only

Reports version, SQLite database location, and storage counters for the RSS/Atom server, helping verify configuration and monitor feed storage.

Instructions

Report version, database location and storage counters.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
nameYes
feedsYes
unreadYes
entriesYes
starredYes
versionYes
databaseYes
transportYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered without the description. The description adds a small amount by naming what is inspected (including a filesystem-level database location, which hints at potentially sensitive output), but it does not characterize cost, freshness, or whether any state is touched.

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 zero filler; every noun maps to something the tool actually returns.

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 zero-parameter read-only probe with annotations and an output schema, this is close to sufficient — the agent knows exactly what it will get back conceptually. It could be marginally more complete by saying the counters are point-in-time snapshots rather than live or cached, but nothing blocks correct invocation.

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 no parameters, so the baseline of 4 applies and there is no argument semantics to explain.

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?

Specific verb ("Report") plus three concrete resources (version, database location, storage counters) make the tool's function unambiguous, and nothing in the feed/entry-oriented sibling list overlaps with it. It stops short of an explicit sibling differentiation statement, which is the only reason it is not a 5.

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 diagnostic/status probe, and the zero-parameter, read-only nature makes selection nearly self-evident. There is no explicit statement of when to call it (e.g., before/after refresh operations) and no exclusions or alternatives named.

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