Skip to main content
Glama

Server info

server_info
Read-only

Call this first to view server version, non-secret configuration, write/delete status, and connected data sources before querying Notion or Supabase content.

Instructions

Describe this server: version, non-secret configuration (including whether writes/deletes are enabled) and the connected data sources. Call this first.

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
configYesNon-secret runtime configuration
sourcesYes
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds genuinely useful context beyond that: the exclusion of secrets, the disclosure of whether writes/deletes are enabled, and the presence of connected data sources. That is real added value, but since the output schema already carries the return shape and no auth, rate-limit, or freshness behavior is discussed, a 3 is the fair level.

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 sentence that front-loads the resource and enumerates contents, followed by a three-word imperative directing usage. No filler, no repetition of the name or title.

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 no-arg read-only inspection tool with full annotation coverage and an output schema, the description covers purpose, contents, and call ordering adequately. It leaves only a minor gap around what the configuration object looks like or how it relates to the health_check sibling.

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?

Zero parameters, so there is nothing for the description to disambiguate; the baseline applies. Nothing in the description adds or detracts from parameter meaning.

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 (describe) and resource (this server) and enumerates the returned contents: version, non-secret configuration, write/delete enablement, and connected data sources. It does not explicitly distinguish itself from the overlapping sibling list_sources, which also surfaces data sources, so it stops short of 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Call this first' gives an explicit, unambiguous ordering directive that tells the agent exactly when to reach for it. It stops short of a 5 because it names no alternatives or exclusions, e.g. when health_check or list_sources would be the better choice.

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

Deploy Server

Other Tools