Skip to main content
Glama

Turn usage counts on or off

set_usage_counts
Destructive

Control Portward's anonymous usage counts: disable them to delete previously collected counts, or enable them to resume counting after user consent.

Instructions

Turn anonymous usage counts off (on=false; the counts kept so far are deleted) or back on (on=true, once the user has been asked; Portward asks them itself).

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": "set_usage_counts"
  }
}

Input Schema

NameRequiredDescriptionDefault
onYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds the crucial specifics: exactly what is destroyed (the counts kept so far are deleted) and that consent must precede re-enabling, with Portward handling the prompt. It does not cover error behavior if consent is refused or whether the toggle is immediate.

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?

One sentence, front-loaded with the action and resource, with the two value branches cleanly parenthesized. No filler text and no repetition of the title.

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 one-parameter toggle with no output schema, this covers the action, the destructive side effect, and the consent prerequisite. Only edge-case behavior (what happens on refusal, whether the deletion is reversible) is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single boolean, so the description carries the full burden and does: it spells out the exact consequence of each value (false deletes stored counts, true re-enables after consent). Nothing about the parameter's meaning is left ambiguous.

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?

States a specific verb pair (turn off/back on) and a specific resource (anonymous usage counts), so the action is unambiguous. It stops short of naming how it differs from the adjacent usage_counts/usage_choice/usage_seen tools, leaving sibling differentiation to inference.

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?

It embeds a usage precondition for the on=true branch ('once the user has been asked'), which is genuinely useful routing information. However, it never says when to reach for this tool rather than the other usage-related tools, so guidance is implied rather than explicit.

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