Skip to main content
Glama

Check whether a request fits

check_request
Read-onlyIdempotent

Describe what the user wants in plain words and get back whether this server can do it, which limits it would hit, and the closest thing it CAN do. Instant, no solve. Use it when unsure the tool fits (seating charts, tournament brackets, round-robin schedules, random draws, repeated rotations, very large lists).

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": {
      "description": "<description>"
    },
    "name": "check_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
descriptionYesThe user's request in their own words, e.g. 'split 30 students into 6 groups, mixed by reading level, keep two friends apart'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: 'Instant, no solve' tells the agent this is a cheap pre-flight check with no execution cost or side effects, which is the key trait an agent needs before deciding to call it. It does not specify output structure in detail, but as a non-mutating check that gap is minor.

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?

The verdict payload is front-loaded in the first clause, followed by the cost characteristic and then the routing trigger. The parenthetical example list is somewhat long, but each item targets a distinct failure mode, so it earns most of its space; trimming one or two would make it tighter.

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

Completeness5/5

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

For a single-parameter, read-only check with rich annotations, the description covers everything needed: what to pass, what comes back, that it is instant and non-executing, and when to reach for it. No output schema exists, yet the return values are described in prose, so nothing material is missing.

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?

Schema coverage is 100% and the schema already carries an example, so the baseline is 3. The description still adds meaning by framing the parameter as free-form user intent ('in plain words') rather than a structured query, and its scenario list hints at what kinds of requests are worth submitting — a small but genuine contribution over the schema.

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

Purpose5/5

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

The description names a specific verb and resource — describe a request in plain words and get a feasibility verdict — and it enumerates the exact return payload: whether the server can do it, which limits apply, and the closest supported alternative. That is far more than a restatement of the name, and it lets an agent distinguish this from make_groups, which would actually perform the work.

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

Usage Guidelines4/5

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

It gives an explicit trigger condition ('Use it when unsure the tool fits') backed by concrete scenario examples (seating charts, tournament brackets, round-robin schedules, very large lists). The 'Instant, no solve' clause implies the exclusion — it does not execute work — but the description never explicitly names the sibling to run once the check passes, so the routing guidance stops just short of complete.

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