Skip to main content
Glama

DiscreteRate

Describe one DRS demo

describe_demo
Read-onlyIdempotent

Full per-demo write-up: history, what it teaches, what to expect from the run_* output. Use this to ground the user before triggering a sim run, or to explain WHY the demo exists when the user asks a conceptual question about it.

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": {
      "demo": "<demo>"
    },
    "name": "describe_demo"
  }
}

Input Schema

NameRequiredDescriptionDefault
demoYesWhich DRS demo to act on. See list_drs_demos for the catalog.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / demo / enum
      Previous value: -[
      -  "fast_slow_drain",
      -  "hamburger_duo",
      -  "valdez_tanker"
      -]New value: +[
      +  "fast_slow_drain",
      +  "hamburger_duo",
      +  "valdez_tanker",
      +  "vegetable_plant",
      +  "chocolate_processing",
      +  "sku_capacity",
      +  "tissue_line"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without help from the description. The description's real contribution is disclosing the return content (history, teaching purpose, expected run_* output), which matters because there is no output schema. It stops short of describing format, depth, or size of the write-up. With annotations carrying the safety profile, a 3 is fair.

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?

Two sentences, front-loaded with what the tool returns before the usage conditions. Every clause carries information: content list, timing ('before triggering a sim run'), and the conceptual-question case. Minor density cost from the em-dash style, but nothing is wasted.

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?

A simple read-only, single-enum-parameter tool whose annotations are complete and whose return content is described in prose in place of a missing output schema. An agent has enough to choose this tool and call it correctly. Only the shape/depth of the returned write-up remains unspecified.

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

Parameters3/5

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

The single 'demo' parameter has 100% schema description coverage, including a complete enum and a pointer to list_drs_demos for the catalog. The description adds no per-parameter detail such as whether an unknown demo value fails or whether the value must match a run_* suffix. Schema coverage does the work here, so baseline 3 applies.

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?

The description gives a specific noun and content scope: 'Full per-demo write-up: history, what it teaches, what to expect from the run_* output.' That clearly separates it from the run_* siblings, which execute simulations rather than describe them. It does not explicitly differentiate itself from the explain_* siblings, which also cover conceptual ground, leaving a small overlap unresolved.

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?

Two concrete triggers are named: 'ground the user before triggering a sim run' and 'explain WHY the demo exists when the user asks a conceptual question.' That effectively routes the agent ahead of the run_* alternatives. There is no explicit when-not guidance, e.g., that this is not the tool for cross-demo comparisons or a catalog listing.

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