Skip to main content
Glama

ReMCP configuration

get_configuration
Read-onlyIdempotent

Use this when the person asks how the hosted ReMCP deployment/account is configured: server version and endpoint, runtime release installed on devices, retention/telemetry policy, hosted limits, and paired-computer versions. Use get_runtime_info for one computer's local runtime roots, policy and limits; use get_system_info for that computer's OS/CPU/memory/disk state.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYes
textYesConcise human-readable result of the tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / data / properties / server / properties / customWidgetsEnabled
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / data / properties / server / properties / rendering
      Added value: +{
      +  "type": "string"
      +}
  2. Added
  3. Removed
  4. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered and needs no restating. The description adds genuinely non-structured context: this reports hosted/account-level configuration rather than per-device state, which is the key behavioral distinction an agent needs. It stops short of noting freshness/caching of the reported values, so not a 5.

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?

Two sentences, zero filler, with the primary use case front-loaded before the routing guidance. The list of returned categories is compact and each item is meaningfully distinct.

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?

A no-argument read tool with an output schema and full annotation coverage needs only trigger conditions and sibling disambiguation, both of which are supplied. Nothing required to invoke it correctly is missing.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. The enumeration of returned configuration categories is a bonus, though it properly belongs to the (present) output schema.

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+resource (get the hosted ReMCP deployment/account configuration) and enumerates the exact contents: server version and endpoint, runtime release, retention/telemetry policy, hosted limits, paired-computer versions. It explicitly distinguishes itself from get_runtime_info and get_system_info, so an agent can route correctly without opening any schema.

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

Usage Guidelines5/5

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

The first sentence gives the trigger condition ('when the person asks how the hosted ReMCP deployment/account is configured'), and the second names two alternatives with their distinct scopes (one computer's local runtime roots/policy/limits; that computer's OS/CPU/memory/disk). Explicit when-to-use plus explicit when-to-use-something-else.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources