Skip to main content
Glama

get_settings

Retrieve embedding completion metrics for Species and Organisms plus active embedding/LLM parameters and context window presets to inspect current model configuration.

Instructions

Get embedding completion metrics for Species and Organisms, 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?

No annotations are supplied, so the description carries the full disclosure burden. It does enumerate what payload categories come back, which is useful, and 'Get' weakly signals a read-only operation, but it says nothing about permissions, whether it triggers embedding work, caching, or how large the response is.

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 three comma-separated content categories and no filler. Every clause corresponds to something the caller receives.

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

Completeness4/5

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

For a zero-parameter, read-only settings tool with no output schema, listing the returned content categories is exactly the right move and covers most of what an agent needs. What's missing is any statement of response shape or how 'embedding completion metrics' should be interpreted.

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; the baseline of 4 applies. The description correctly implies the tool is unfiltered and returns a fixed settings snapshot.

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') plus three enumerated resource categories: embedding completion metrics for Species and Organisms, active embedding/LLM parameters, and context window presets. The scope is concrete enough that an agent knows this returns configuration/diagnostic state rather than entity data. It doesn't name a sibling to contrast with, so it stops short of a 5.

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 explicit when-to-use guidance, no preconditions, and no routing to alternatives such as get_platform_status or get_openapi_spec, which plausibly overlap in the 'system information' space. The only hint is the implied 'check embedding progress' use case embedded in the resource list.

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