Skip to main content
Glama

rest

Read-onlyIdempotent

Read a fresh short scene during an active visit (a deliberate pause). Requires session. Returns immediately; does not extend the visit or block anything.

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": {
      "session": "<session>"
    },
    "name": "rest"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNo
sessionYesPrivate bearer capability returned by check_in. Never put it in a URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, closed-world. The description adds genuinely new behavioral facts: session is mandatory and the call returns immediately without extending the visit or blocking anything — important for a tool that might otherwise look like it consumes visit time.

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?

Three short sentences, front-loaded with the purpose, then the prerequisite, then the side-effect guarantees. No filler.

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?

For a two-parameter read tool with rich annotations and no output schema, the description covers prerequisites and side effects but leaves the return value ('a fresh short scene') and the `host` flag unexplained. An agent can call it, but not predict what it gets back or what the second parameter does.

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

Parameters2/5

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

Schema coverage is only 50%: `session` is documented in the schema, but the `host` boolean has no description anywhere. The description only restates that a session is required and adds nothing about what `host` toggles, so it fails to compensate for the coverage gap.

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 (read) and resource (a fresh short scene) plus the delimiting condition (during an active visit, a deliberate pause). It is distinguishable from deep_rest_report and linger, though it never names a sibling, so the differentiation relies on the agent inferring from the words 'short'/'pause'.

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?

'During an active visit' and 'Requires session' imply when it is callable, and 'does not extend the visit or block anything' tells the agent the cost of calling it. However, no alternative is named (linger, deep_rest_report, check_out), so the choice between them is left to inference.

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