Skip to main content
Glama

Optimatika Optimisation Service

This server's limits and solvers

environment
Read-onlyIdempotent

Reports what a model solved here may be: how large, how long it may run, and which solvers are available.

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": "environment"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add content context, which it does by naming what is reported: size limits, runtime limits and available solvers. It does not state response shape or whether limits are per-call or per-session, a modest remaining gap.

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?

One sentence with no filler, front-loading the purpose. The only cost is slightly tangled syntax in the clause about what a solved model may be, which could be stated more directly.

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-param, no-output-schema informational tool, the description conveys the three things an agent needs to know it can get here (size limits, runtime limits, solver list). A note that it is free and safe to call at any time would close the last gap.

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?

With zero parameters, there is nothing to disambiguate, and the schema is fully self-describing (additionalProperties false, no inputs). The description correctly avoids inventing parameter discussion, matching the baseline for a no-arg tool.

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?

States a specific verb ("Reports") and a concrete resource: server limits (size, runtime) and available solvers. This clearly distinguishes it from the action siblings solve and translate, though the phrasing "what a model solved here may be" is grammatically awkward and takes a second read.

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 infer it should consult this before constrained work such as solve, since it exposes size and runtime bounds. There is no explicit when-to-use, when-not, or named alternative, so the guidance remains inference rather than instruction.

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