Skip to main content
Glama

get_config

Retrieve the current configuration to check which integrations are connected and which feature flags are enabled before troubleshooting or adjusting your setup.

Instructions

Returns the current LMCP configuration: connected integrations and feature flags.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.352
  2. Removedv3.0.341
  3. Addedv3.0.165

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does signal a read-style operation ('Returns') and names the two categories of data returned, which is meaningful behavioral context. However, it never states whether the payload can include sensitive material (tokens, credentials, account identifiers) or whether the call has any side effects, which matters for a configuration dump.

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 front-loaded sentence with no filler, and the two returned content groups are placed where an agent scanning the description will see them first. Nothing is repeated or padded.

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?

With zero parameters this is a simple tool, but it has no output schema and no annotations, so the description is the only source of information about the result. It names the broad categories but not the shape, key names, or nesting of the returned configuration, leaving the agent to discover the structure at call time.

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 baseline is 4. The description correctly implies a no-argument, whole-configuration read and does not invent parameter behavior. There is nothing further it could add on this dimension.

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 gives a specific verb and resource ('Returns the current LMCP configuration') and enumerates the two content groups it exposes: connected integrations and feature flags. That is clearer than a bare name restatement. It stops short of distinguishing itself from similarly named siblings such as lmcp_state, lmcp_doctor, or permissions_status, so an agent cannot be certain which one to call.

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 guidance and no mention of alternatives, despite a crowded set of config/diagnostic siblings (lmcp_state, lmcp_doctor, run_diagnostics, permissions_status, list_accounts). The only implied usage is 'read current config', which the agent must infer from the verb. No exclusions or prerequisites are stated.

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