Skip to main content
Glama
Sign In
tuskr-mcp

tuskr-mcp

by Zapkid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_case_steps

Retrieve normalized, ordered steps for a specific test case by providing the app name and case key or ID.

Instructions

Get normalized ordered steps for one case.

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": {
      "app_name": "<app_name>",
      "case_key_or_id": "<case_key_or_id>"
    },
    "name": "get_case_steps"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_nameYes
case_key_or_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. The description mentions 'normalized' and 'ordered' steps, which provides some behavioral insight, but does not disclose read-only status, rate limits, or authentication needs.

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 description is a single sentence, which is concise but lacks sufficient detail for the parameters. It is front-loaded with the purpose but sacrifices completeness.

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?

An output schema exists, so return values need not be explained. However, the description fails to clarify parameter semantics, and given the tool's simplicity, this is a notable gap.

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

Parameters1/5

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

The description offers no explanation of the two required parameters ('app_name' and 'case_key_or_id'), which have 0% schema description coverage. The agent must infer their meaning from names alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get', the specific resource 'normalized ordered steps', and the scope 'for one case'. It distinguishes from sibling tools like 'get_test_case' which likely returns case details rather than steps.

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?

No guidance is given on when to use this tool versus alternatives such as 'get_test_case' or 'get_test_cases_by_section'. The agent is not informed about prerequisites or context.

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

Deploy Server

Other Tools