Skip to main content
Glama

Get Server Config

get_server_config
Read-onlyIdempotent

Inspect this server's settings and token presence without revealing it. Read-only and works before a token is set, so run it first to diagnose setup problems.

Instructions

Show this server's settings (school URL, tool profile and every profile you can switch to, write mode, cache, time zone, download folder) and whether a token is present, without revealing it. Read-only, makes no Canvas calls and works before a token is set, so use it first to diagnose setup problems.

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_server_config"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, but the description adds behavior the annotations cannot express: 'makes no Canvas calls', 'works before a token is set', and that token presence is reported 'without revealing it'. That last point is important security context an agent would otherwise not know, and it also implicitly describes the return payload.

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?

One dense sentence with the returned-fields parenthetical front-loaded before the usage instruction, and no filler. It is slightly run-on, stacking a long field parenthetical plus three behavioral clauses, but every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description effectively enumerates the returned settings plus the token-presence flag, so an agent knows what to expect. Safety, pre-auth availability, and diagnostic purpose are all covered for a simple zero-parameter tool.

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 there is nothing for the description to disambiguate; baseline for a zero-param tool applies. The description correctly avoids inventing parameters and instead spends its words on output content.

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?

States a specific verb ('Show') and resource ('this server's settings') and then enumerates the exact fields returned: school URL, tool profile and switchable profiles, write mode, cache, time zone, download folder, token presence. This is clearly distinguished from the get_* Canvas resource siblings because it is explicitly about the server itself, not course data.

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?

Gives an explicit routing instruction: 'use it first to diagnose setup problems', which tells the agent when to reach for this over any Canvas data tool. It also removes a common blocker by noting it 'works before a token is set'. It does not state a when-not, but for a zero-parameter introspection tool there is little competing alternative.

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