Skip to main content
Glama
Sign In
umbra

umbra

by lxchx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Set Verbosity

set_verbosity

Toggle response minification between compact and full modes to get raw, untruncated bytes for byte-exact operations, then switch back to compact output.

Instructions

Toggle response minification. 'compact'=default (drops nones, columnar, trunc). 'full'=raw bytes, no trunc. Flip 'full' for byte-exact ops, then back.

Ex: set_verbosity('full') → {"prev":"compact","now":"full"}

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

Input Schema

NameRequiredDescriptionDefault
levelNocompact

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden well by explaining that 'compact' drops nulls, uses columnar output, and truncates, while 'full' returns raw bytes without truncation. It also shows the return shape, though it leaves the setting's scope or persistence implicit.

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 compact, front-loaded with the core behavior, and each sentence adds useful information. The example is brief and directly relevant.

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 simple one-parameter setting tool with an output schema, the description covers modes, default, and intended use. It could be more complete by stating whether the setting is session-scoped, global, or persistent.

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 description coverage is 0%, but the description fully compensates by defining both enum values and the default. It explains what each mode changes, which is more than the bare enum provides.

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?

States a specific action and resource: toggling response minification, with both modes named and their effects summarized. An agent can distinguish this as a server-response formatting control rather than a browser action.

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?

Explicitly recommends using 'full' for byte-exact operations and then switching back. It gives clear usage context but does not spell out exclusions or alternatives.

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