Skip to main content
Glama
Sign In
discp

discp

by SharimAli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_bot_info

Retrieve current Discord bot status, username, ping, server count, and uptime to monitor bot health and performance.

Instructions

Get current bot application status, username, ping, server count, and uptime

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description must carry behavioral disclosure. Its phrasing 'Get current ... status' implies a read-only, side-effect-free, no-argument call, which is consistent behavior, but it never explicitly states read-only/non-destructive or whether it hits a live API with rate limits. It is adequate but leaves the safety profile to inference.

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 front-loaded sentence with no filler. The enumerated outputs earn their place by telling the agent what it will receive. Not a 5 only because it is quite terse and could route the agent better without added bulk.

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?

For a zero-parameter read tool with no annotations and no output schema, the description covers what the tool returns and implies a safe read, which is mostly sufficient. However, with no structured safety hints it could do more, and it lacks any guidance distinguishing it from sibling info-getters.

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?

There are zero parameters, which earns the baseline of 4 under the rubric. The description neither needs nor provides parameter detail, and it correctly implies a self-contained call with no required input.

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 clear verb+resource: 'Get current bot application status...'. It enumerates exactly what information the tool returns (status, username, ping, server count, uptime), which lets an agent distinguish it from siblings like get_user_info or get_server_info. It stops short of 5 because it does not explicitly name or differentiate from those nearest siblings, which also return identity/status data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. The description lists outputs but never states the situation that should trigger this tool versus alternatives such as get_user_info or get_server_info.

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