Skip to main content
Glama

Manage property lists

spur_manage_property_list
Destructive

Read a list and its stats, rename it, delete it, remove members, or copy/move members to another list. Moves add to the destination before removing from the source; a partial failure reports progress. Does not send outreach.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered structurally. The description adds genuinely non-obvious behavior beyond that: moves add to the destination before removing from the source, and partial failures report progress rather than silently rolling back. It still does not say what happens to the member properties when a list is deleted or whether a failed move can leave duplicates, which keeps it from 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?

Two sentences, front-loaded with the action inventory, followed by the non-obvious move and failure semantics and a scope boundary. No restatement of the title, no filler, and each sentence contributes distinct information.

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 six-branch oneOf dispatcher with no output schema and destructive annotations, the definition covers every action branch and the trickiest failure mode. The only shortfall is that the update branch is described as "rename it" while the schema also allows changing the description field, a small mismatch an agent could miss.

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 description coverage is 100%, so the schema already documents every branch, including the confirm flag's explicit approval requirement. The description adds no parameter-level detail — it never mentions list_id, destination_list_id, property_ids, or the rename/description fields. Baseline 3 applies when the schema carries the parameter burden.

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?

The description enumerates the exact operations bundled into this dispatcher: read a list and its stats, rename, delete, remove members, copy/move members. That is a specific verb-plus-resource statement that lets an agent map each action to the intended effect. It stops short of naming a sibling it is not (e.g., create/list/add-properties tools), so differentiation is implied by scope rather than stated.

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?

"Does not send outreach" gives one useful exclusion, and the action list implies when each mode applies, but there is no explicit routing guidance such as when to prefer this tool over adding properties via a separate add tool or creating lists elsewhere. An agent must infer selection from the action names and the schema's oneOf branches. Adequate but with a clear gap in when-to-use framing.

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