Skip to main content
Glama

benchmark

Time shell commands with warmup and repeated runs, then report mean±SD, median, p95 and comparisons to spot performance differences.

Instructions

Time shell commands: warmup, N runs, mean±sd, median, p95, comparison.

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": {
      "commands": "<commands>"
    },
    "name": "benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNo
runsNo
warmupNo
commandsYes
timeout_sNo
max_total_sNo
ignore_failureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that commands are executed repeatedly with warmup and reports several timing metrics, but says nothing about failure handling, timeout behavior, total-duration caps, or the risks of executing arbitrary shell commands.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of padding, but it is a fragment that under-specifies the tool. Conciseness here comes at the cost of missing operational detail rather than being a model of efficient structure.

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

Completeness2/5

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

For a seven-parameter shell-execution tool with no annotations, no parameter descriptions, and no output schema, the definition is too thin. It leaves out timeout controls, failure semantics, working directory behavior, and total runtime limits that an agent needs before invoking it safely.

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 description coverage is 0% across seven parameters. The description names only implicit concepts like warmup, runs, and commands; it does not explain cwd, timeout_s, max_total_s, or ignore_failure, all of which are undocumented in both the schema and the description.

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 and resource: 'Time shell commands', plus the metrics it reports (mean±sd, median, p95, comparison). It is clear enough to distinguish from unrelated sibling utility tools, though it does not explicitly name alternatives or contrast itself with any sibling.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no preconditions, and no alternatives. It implies benchmarking commands, but an agent gets no help deciding when this tool is appropriate versus running a shell command directly or using another utility.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.