Skip to main content
Glama

Change tracing settings

update_tracing_settings
Idempotent

Set the share of traces the SDKs keep, and the hosts the app's SDK sends trace headers to (replacing the list). A field you leave out keeps its value. SDKs read it from their config within a minute. Only works when the app allows MCP writes.

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

Input Schema

NameRequiredDescriptionDefault
sample_rateNo0 to 1; 1 keeps every trace
propagate_toNoHosts or origins: api.example.com, *.example.com, https://api.example.com:8443. [] clears it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses three behavioral traits the agent could not infer: partial-update semantics (omitted fields retain their value), that propagate_to replaces rather than merges the list, and the roughly one-minute propagation delay plus the MCP-write permission gate. These are exactly the operational details an agent needs before mutating config.

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?

Three compact sentences, front-loaded with what is being set, followed by update semantics and then the operational caveats. No filler or repetition of the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, non-destructive, idempotent mutation with no output schema, the description covers purpose, partial-update behavior, list replacement, permission requirement, and propagation latency. Nothing material is missing for correct invocation.

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?

Schema coverage is 100%, so the baseline is 3; the description earns a point by clarifying that both parameters are optional and that leaving one out preserves the existing value, and by flagging the replace-the-whole-list semantics of propagate_to. It does not restate the 0-1 range or host format, but the schema already covers those.

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 names a specific verb and both resources being changed: the trace sample rate kept by SDKs and the list of hosts receiving trace headers. No sibling in the catalog touches tracing configuration, so there is no ambiguity to resolve, and an agent can act from the first sentence alone.

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 a clear precondition ("Only works when the app allows MCP writes") and describes the effect timeline (SDKs pick it up within a minute), which tells the agent when a call is valid and how quickly to expect results. It does not state explicit exclusions or alternatives, but no sibling covers this surface, so the omission is minor.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources