Skip to main content
Glama

scope_update

Idempotent

Update an existing scope’s rules or description using the same validation as creation to keep scope definitions accurate and consistent.

Instructions

Update a scope's rules and/or description (same validation as create).

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

Input Schema

NameRequiredDescriptionDefault
nameYes
rulesNo
descriptionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is largely covered. The description adds one useful behavioral note—validation mirrors creation—but says nothing about partial-update semantics, notably whether omitting rules or description leaves them untouched while passing null clears them. For a mutation with defaulted nullable fields, that ambiguity is a real gap.

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?

A single front-loaded sentence with no filler. Its brevity is appropriate, though the parenthetical reference to create is a compressed dependency the reader must resolve by opening another tool.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and annotations cover the safety contract. However, a mutation tool with fully undocumented parameters and unclear null/omit semantics leaves the agent guessing on the one thing that matters most: how to avoid accidentally wiping a field.

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?

Schema description coverage is 0% across three parameters, so the description must carry the load and it does not. Beyond naming the two fields, it never explains the shape of `rules`, why `name` is the only required field, or what the null defaults do to existing values.

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+resource: updates a scope's rules and/or description. It clearly identifies the two mutable fields, though it doesn't differentiate this from the many sibling update_* tools (policy_update, update_binding, update_concept, update_entity) or explain what a "scope" is in this system.

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

Usage Guidelines2/5

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

No explicit when-to-use guidance or prerequisites are given. The parenthetical "(same validation as create)" implicitly points at scope_create for the validation contract and implies the scope must already exist, but the agent gets no statement of when to prefer this over scope_create or how it relates to scope_bind_caller/scope_delete.

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