Skip to main content
Glama

toggle_schema

Enable or disable a schema without deleting it, preventing inactive schemas from loading into the agent. Set the enabled state or omit it to toggle the current state.

Instructions

Enable or disable a schema without deleting it. Inactive schemas are not loaded by the agent. Set enabled for the desired state; omitting it toggles the current state. Concurrent calls can race, so verify the returned is_active value.

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": {
      "schema_id": "<schema_id>"
    },
    "name": "toggle_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNotrue = ativa; false = desativa. Omitir inverte o estado atual (repetir a chamada desfaz).
schema_idYesSchema UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.2.4
    • addedInput schema / properties / enabled
      Added value: +{
      +  "description": "true = ativa; false = desativa. Omitir inverte o estado atual (repetir a chamada desfaz).",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / schema_id / description
      Previous value: -"UUID do schema"New value: +"Schema UUID"
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, and the description meaningfully builds on that: omitting `enabled` inverts state (explaining the non-idempotent hint), and concurrent calls can race, so the agent should verify the returned is_active. It does not mention permission requirements or side effects on sessions already using the schema, keeping it below a 5.

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 short sentences, front-loaded with the core action, then the rationale, then the parameter contract, then the concurrency caveat. No sentence is filler.

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 two-parameter, no-output-schema tool, the description covers the action, the state semantics, the non-idempotency, and the need to check the returned is_active. Only the permission/auth surface and effects on in-flight consumers are unaddressed, which is a minor gap.

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

Parameters3/5

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

Schema coverage is 100%, and the schema already documents that `enabled` means true=activate, false=deactivate, and that omission inverts the current state. The description restates rather than extends that, so the baseline 3 applies despite the useful emphasis on the toggle semantics.

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 verb (enable/disable) and resource (schema) plus a scoping constraint ('without deleting it') that separates it from delete_schema and update_schema. An agent can tell what this does and what it does not do without opening the schema.

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?

Gives clear operating context: inactive schemas are not loaded by the agent, which explains why one would toggle rather than delete. It implies the deletion alternative but never explicitly says 'use delete_schema to remove' or names exclusions, so it stops short of full when/when-not routing.

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