Skip to main content
Glama

Report a setup step to Cuttr

setup_step

Only when the cuttr-test instructions say so: tells the member's setup page that the test edit finished.

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": {
      "step": "<step>"
    },
    "name": "setup_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepYes
secondsNoHow long the test edit took

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the behavioral effect (it writes to the member's setup page, marking the test edit finished), but omits idempotency, whether repeat calls advance multiple steps, required identity/permissions, and error behavior on a mutation endpoint.

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?

A single sentence with the gating condition front-loaded before the effect, which is the right ordering for a conditionally callable tool. No filler, though the colon construction makes it slightly telegraphic.

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, no-output-schema tool this covers the essential trigger and effect. It leaves open what happens after reporting (does the setup page advance?), whether the member must be identified by session, and what an invalid or repeated call returns, which matters because no annotations and no output schema provide that context elsewhere.

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 schema documents the optional seconds parameter and constrains step to a single enum value, so the parameter shape is largely self-explanatory. The description's phrase 'the test edit' implicitly motivates step='test' but adds no syntax, units, or default guidance beyond the schema.

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: reporting a completed 'test edit' to the member's setup page. The scope is clear enough to distinguish it from siblings such as report_problem or log_video, though it never names an alternative explicitly.

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?

Gives an explicit negative gate: only call this when the cuttr-test instructions say so, which is a genuine when-to-use constraint. It stops short of naming what to use instead if setup reporting is needed elsewhere in the flow.

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