Skip to main content
Glama

Maintain owner records

spur_manage_owner
Destructive

Create/edit an owner, correct manual contacts, link a saved property, soft-delete, or preview enrichment without running it. Owner/property ownership is checked before linking.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds value beyond them: the delete is a soft-delete (implying recoverability), and linking validates owner/property ownership first, which is a precondition the agent would not otherwise know. It does not clarify that the enrichment_preview branch is a read-only operation inside an otherwise destructive tool, nor what the ownership check failure looks like.

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?

Two sentences, with the operation list front-loaded and every clause mapping to a real action variant, so nothing is filler. The action list is a dense run-on rather than a structured enumeration, but it reads efficiently and wastes no words.

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 multi-branch destructive tool with no output schema, the description covers the key risks (soft-delete, ownership validation, preview-before-enrich). Gaps remain around the explicit confirmation requirement for delete and what any branch returns, but the safety-critical context is present.

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 effectively complete, so the schema carries the parameter burden and baseline is 3. The prose does clarify intent for the less obvious action names (manual contacts = correcting contacts, enrichment_preview = preview without running), but it never mentions the required confirm:true gate on delete or the optional is_occupied/ownership_type fields on link_property.

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 names a specific resource (owner) and enumerates the concrete operations: create/edit, correct manual contacts, link a saved property, soft-delete, preview enrichment. This maps cleanly onto the oneOf action variants, so an agent can tell what the tool covers. It does not explicitly distinguish itself from the read sibling spur_get_owner, which keeps it from a 5.

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?

Usage is implied by the enumeration: preview enrichment is framed as a dry run before the real thing, and the ownership check is stated as a precondition for linking. There is no explicit when-not guidance, no statement about when to prefer spur_get_owner for reads, and no mention of when delete should be considered versus trash.

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