Skip to main content
Glama

Server info

discord_server_info
Read-only

Retrieves the bot identity, connected Discord server, and access policy details such as read-only mode, write auditing, and mention rules.

Instructions

Who this bot is, which Discord server it is connected to, and what it is allowed to do (read-only mode, whether writes are audited, mention policy).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context beyond them by disclosing that the tool reveals operational policy (read-only mode state, write auditing, mention policy), which tells the agent what kind of configuration knowledge it gains rather than just that the call is safe.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence covering three payload areas, front-loaded with the most important item (who the bot is). The parenthetical list is scannable. Slightly fragmentary grammar rather than a clean declarative sentence keeps it from a 5.

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?

With no parameters, no output schema, and annotations covering the safety profile, the description carries most of the remaining burden and does so adequately by enumerating the categories of information returned. It omits return shape and exact field names, which is acceptable given there is no output schema to align with, but a one-line note on structure would have made it complete.

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 zero parameters, so the schema imposes no semantic burden and the baseline is 4. The description correctly spends no words on argument semantics, which is the right call for a parameterless call.

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?

The description names the specific resource and scope precisely: bot identity, the connected Discord server, and the bot's permission/policy state (read-only mode, audit of writes, mention policy). That is enough to distinguish it from write/admin siblings, but it never explicitly contrasts it with the overlapping discord_admin_get_server, so differentiation is left implicit.

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?

No explicit when-to-use or when-not-to-use statement is given. The mention of 'read-only mode' and 'whether writes are audited' hints that this is a pre-flight check to run before attempting mutations, but the agent must infer that; there are no stated exclusions or named alternatives.

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