Skip to main content
Glama
Sign In
Grok Gadgets Gateway

Grok Gadgets Gateway

by adidshaft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

gadgets_diagnostics

Read-only

Generate an allowlisted support report that excludes tokens, device state, arguments, and raw errors to enable safe diagnostics.

Instructions

Get an allowlisted support report without tokens, state, arguments or raw errors.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gadgets_diagnostics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, covering the safety profile. The description adds meaningful value by disclosing that output is redacted ('without tokens, state, arguments or raw errors'), which tells the agent the report is sanitized. However, it says nothing about report size, format, or what it does contain.

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, front-loaded sentence with no filler. The trailing redaction clause is terse to the point of being slightly cryptic, but it earns its place by signaling sanitized output.

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?

With no parameters and no output schema, the description carries the burden of explaining what the report contains, yet it only describes what is excluded, not what an agent will actually get back. Annotations cover safety, but the return-value gap leaves the definition only minimally viable.

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?

The tool takes zero parameters and schema coverage is 100%, so there is nothing for the description to clarify. Baseline 4 applies for a no-parameter tool.

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

Purpose3/5

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

States the verb ('Get') and the object ('an allowlisted support report'), but 'support report' is vague about what diagnostic content is actually returned. It does not differentiate from siblings like gadgets_get_state or gadgets_read_events, so an agent cannot tell why it would pick this over reading state directly.

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?

There is no guidance on when to use this tool versus the sibling diagnostics-adjacent tools (get_state, read_events). The description implies a diagnostic/support purpose but gives no trigger condition or exclusion.

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