Samuelz® Operations

Einzelnen Fall kennzeichnen

mark_case_as_test

Idempotent

Only after the Owner explicitly identifies this exact case as a test: apply the existing canonical test classification using caseId and the unchanged revision from get_case_test_review. Reason is required. Excludes this case from operational work and measured demand without editing its reservation, contacts, payment or conversation. Older genuine cases for the same contact remain. Paid, refunded, assigned, invoiced or otherwise committed cases are blocked. A stale review requires rereading and renewed intent; never replace its revision automatically. On an uncertain response read the same review; do not invent a retry. An already classified case returns unchanged with no second audit event. No sending, cancellation or provider effect.

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": {
      "caseId": "<caseId>",
      "expectedRevision": "<expectedRevision>",
      "reason": "<reason>"
    },
    "name": "mark_case_as_test"
  }
}

Input Schema

Name	Required	Description	Default
`caseId`	Yes
`reason`	Yes
`expectedRevision`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations by enumerating what is NOT touched (reservation, contacts, payment, conversation), what stays intact (older genuine cases for the same contact), and what side effects exist (an audit event, suppressed on repeat). It also discloses idempotent behavior concretely ('an already classified case returns unchanged with no second audit event') and confirms no provider-side effect.

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?

Front-loaded with the authorization gate before any mechanics, and most sentences carry distinct rules. There is mild redundancy between 'without editing its reservation, contacts, payment or conversation' and the closing 'No sending, cancellation or provider effect', and the telegraphic phrasing takes effort to parse.

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 output schema, the description still covers return behavior for the idempotent case, audit emission, blocked states, and retry semantics, which is strong for a 3-parameter mutation. It does not describe what a successful first-time response contains, leaving the agent to infer the shape.

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?

Schema coverage is 0%, so the description must carry the load: it explains that expectedRevision must be the unchanged revision obtained from get_case_test_review and must never be substituted, which is the critical meaning for that parameter. reason is only stated as required without guidance on content, and the 64-hex format for expectedRevision is left to the schema.

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?

States a specific verb and resource ('apply the existing canonical test classification') and pins the exact identifier source ('caseId and the unchanged revision from get_case_test_review'), which cleanly separates it from the sibling review-reader. The downstream effect ('excludes this case from operational work and measured demand') tells the agent what the operation actually accomplishes.

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

Usage Guidelines5/5

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

Gives an explicit gate ('Only after the Owner explicitly identifies this exact case as a test') plus negative conditions ('Paid, refunded, assigned, invoiced or otherwise committed cases are blocked'). It also routes the agent: a stale revision means re-reading the review and re-confirming intent, and an uncertain response means re-reading the same review rather than inventing a retry.

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

All Samuelz® Operations tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?