Skip to main content
Glama

Panel: usage counts on or off

usage_choice
Destructive

Turn usage counts on or off in the results panel to control whether usage data appears in query results. App-only.

Instructions

The user turned usage counts on or off in the results panel. App-only.

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": {
      "on": "<on>"
    },
    "name": "usage_choice"
  }
}

Input Schema

NameRequiredDescriptionDefault
onYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, so the schema already carries the risk profile; the description adds nothing about what is altered, whether the preference persists, or what the panel does afterward. There is mild tension between "user turned usage counts on or off" and a destructive flag, but not a direct contradiction.

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?

Two short sentences, the subject-panel scope is front-loaded, and there is no padding. Brevity here is efficient rather than evasive, though the second sentence carries most of the actionable information.

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?

With no output schema, one undocumented parameter, and a destructive annotation, the description should at minimum clarify whether this is an event or a setter and what changes as a result. As written an agent cannot confidently decide to call it or understand its effect.

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?

There is one required boolean parameter "on" with 0% schema description coverage, and the description only echoes "on or off" without explaining what true/false means or what each state changes. It fails to compensate for the documentation gap in the schema.

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?

"The user turned usage counts on or off in the results panel" is close to a restatement of the title "Panel: usage counts on or off". It hints at an event/notification semantic (the user did something) rather than an action, but never makes that explicit, leaving ambiguous whether the tool applies the toggle or merely reports that it happened.

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

Usage Guidelines3/5

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

"App-only" is a genuine invocation constraint — it signals this belongs to an embedded app surface rather than general agent use. However, it never names or excludes the obvious sibling set_usage_counts, nor states under what conditions an agent should call this instead of that.

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