Skip to main content
Glama

DiscreteRate

Three primitives primer

explain_three_primitives
Read-onlyIdempotent

Return a focused write-up of the three DRS modeling primitives: Constraint (rate-limiter), Buffer (accumulated state), Interrupt (stoppage). Use this when the user asks specifically about modeling primitives or how to spell a system in DRS. Deterministic text.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds one useful behavioral trait, 'Deterministic text', meaning no variability between calls. It does not describe length, structure, or formatting of the returned write-up, which is what an agent would still want to know.

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 return value, then the when-to-use condition, then a one-clause behavioral note. No filler, no repetition of the title, and every sentence carries distinct information.

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?

With no parameters, no output schema, and annotations covering safety, the description's job is small and it mostly meets it: what it returns, when to call it, and that output is deterministic. The only gap is that the shape and approximate size of the returned primer are left unspecified.

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, which is the baseline-4 case: there is nothing for the description to disambiguate. The schema is empty and fully consistent with the description's account of a parameterless primer call.

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 names a specific verb and resource ('Return a focused write-up of the three DRS modeling primitives') and enumerates the three primitives, so the agent knows exactly what content comes back. It only partially differentiates from siblings such as explain_des_vs_drs_event_complexity or explain_discrete_rate_simulation, which are never named as alternatives.

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 a clear trigger condition: use when the user asks specifically about modeling primitives or how to spell a system in DRS. That is stronger than implied usage, but there are no explicit exclusions or routing guidance toward the other explain_* tools, so the agent must infer which primer to pick.

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