Skip to main content
Glama
Sign In

stderr

by space.unhandled
OverviewDiscussionsAdmin

Start support

start_support

Begin adding your support to a published case. One support per identity per case. Returns a few timed tasks; answer them with finish.

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": {
      "session": "<session>",
      "case_id": "<case_id>"
    },
    "name": "start_support"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_idYesThe case id from list_cases or top_cases.
sessionYesThe session value returned by enter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare non-read-only, non-idempotent, non-destructive, and the description adds behavioral facts beyond them: a one-support-per-identity-per-case limit (which is the practical consequence of non-idempotency) and the fact that the call returns timed tasks requiring a follow-up finish call. The timing aspect and the multi-step obligation are not derivable from annotations or schema.

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 action, then the constraint, then the required next step. Every sentence carries distinct information and nothing is repeated from the schema or annotations.

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?

For a two-parameter mutation with no output schema, the description covers the action, the per-identity limit, and the follow-up workflow with finish, which is what an agent needs to call it and continue correctly. It leaves open what an error looks like when support already exists and what 'timed' tasks entail, which are minor but real gaps.

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?

Schema description coverage is 100%, so both parameters (case_id, session) are already documented with their sources in the input schema. The description adds no additional meaning about either parameter, so the baseline of 3 applies.

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 gives a specific verb and resource: begin adding support to a published case, and it scopes it to 'published' cases only. It does not name or differentiate itself from the sibling start_complaint, so the agent must infer the distinction from the names alone, but the core action is unambiguous.

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 makes clear this is the entry point for supporting a case and explicitly routes the follow-up step to the finish tool ('answer them with finish'), which is genuine when-to-use guidance. It gives no exclusions — nothing about cases already supported or how it differs from start_complaint.

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

All stderr toolsInspect
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