Skip to main content
Glama

get_settings

Retrieve embedding completion metrics for SubatomicParticles and QuantumStates, active embedding/LLM parameters, and context window presets.

Instructions

Get embedding completion metrics for SubatomicParticles and QuantumStates, active embedding/LLM parameters, and context window presets.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; 'Get' does imply a non-mutating read and it names the three content categories returned. However, it says nothing about permissions needed, whether the metrics are workspace-scoped or global, or whether settings can ever be changed here.

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, but it is a bare list of three noun phrases rather than structured explanation. Nothing extraneous, though little is prioritized.

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?

No output schema exists, so the description must characterize the return value, and it does so only at a high level. Terms like 'embedding completion metrics' and 'context window presets' are left undefined, which leaves an agent guessing at the shape of the response for a tool whose sole value is its returned data.

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 schema and description are consistent in presenting a parameterless call.

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?

Specific verb 'Get' with a concrete resource: embedding completion metrics, active embedding/LLM parameters, and context window presets. It is clearly a read-only settings/metrics tool, though it never explicitly contrasts itself with nearby readers like get_platform_status or get_openapi_spec.

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

Usage Guidelines3/5

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

Usage is only implied — an agent can reasonably infer it should call this when it needs current embedding/LLM configuration or preset values. There is no explicit when-to-use, when-not-to-use, or named alternative, and no mention that the tool yields no results for other entities.

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