Skip to main content
Glama

get_settings

Retrieve the stored settings record for a given scope, scope ID, and repository, returning None when it is unset.

Instructions

Return the stored record for one layer, or record: None when unset.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "scope": "<scope>",
      "scope_id": "<scope_id>",
      "repo": "<repo>"
    },
    "name": "get_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYes
scopeYes
scope_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.10.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose one useful edge case (returns record: None when unset), but says nothing about read-only semantics, permissions, or what the returned record contains, leaving most behavior implicit.

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; it states the return behavior immediately. Brevity here is appropriate, though the same brevity contributes to the semantic gaps elsewhere.

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

Completeness2/5

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

A 3-required-parameter lookup tool with no annotations and no output schema needs the description to explain parameter meaning and lookup semantics. The description covers the unset case but leaves the three required inputs and the meaning of "layer" entirely unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All three parameters are required with 0% schema description coverage, and the description never mentions scope, scope_id, or repo or explains how they identify a layer. With no schema documentation to fall back on, this is a clear gap the description should have filled.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Return the stored record for one layer" gives a verb and a resource, but "layer" is undefined jargon that does not map onto the actual parameters (scope, scope_id, repo) and does not distinguish this tool from the sibling list_settings or get_effective_config. An agent understands it reads stored settings, but not precisely which.

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, no preconditions, and no mention of the plausible alternatives (list_settings, get_effective_config) that appear among the siblings. The agent must infer selection from the name alone.

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