Statuz

Send feedback

feedback

Send feedback or a bug report to the Statuz team. Use it when someone wants to report a bug or share an idea. Only the team reads it. Read-only credentials can send it.

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": {
      "message": "<message>"
    },
    "name": "feedback"
  }
}

Input Schema

Name	Required	Description	Default
`org`	No	Org id (default: your first org)
`kind`	No	bug, idea, confusing, praise or other	other
`page`	No
`task`	No	What you were trying to do
`agent`	No	Your agent, if you are one
`email`	No	Where we can reply, when not signed in
`error`	No	The error it gave
`model`	No	Your model, if you are one
`client`	No
`command`	No	The command it is about, like posts.create
`message`	Yes
`screenshot`	No	A JPEG or PNG data URL; the CLI takes a file: --screenshot shot.png

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond annotations, it discloses that only the team reads the submission and that read-only credentials can send it, adding useful privacy and authorization context. It does not explain idempotency or response behavior, but annotations cover the non-destructive and non-idempotent hints.

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?

The description is four short sentences, front-loaded with purpose and followed by usage, privacy, and authorization notes. Every sentence adds useful information without repetition.

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?

It covers purpose, when to use it, audience, and authorization, which are important for a feedback tool. However, for a tool with 12 parameters, nested objects, and no output schema, it omits useful invocation context about what diagnostic details to include.

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?

The description adds no parameter guidance despite 12 parameters, nested page/client objects, and only 75% schema description coverage. It does not mention the required message field, the kind enum, or the optional diagnostic fields such as page, error, command, or screenshot.

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 states a specific verb and resource: sending feedback or a bug report to the Statuz team. It clearly distinguishes this from all sibling tools, which are account, media, posts, and cloud operations.

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 gives an explicit usage trigger: use it when someone wants to report a bug or share an idea. It lacks when-not guidance or alternatives, but no obvious sibling competes with this tool.

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

All Statuz 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?