Skip to main content
Glama

Select field source or primary contact

spur_select_property_field
Destructive

Choose a stored observation, lock a field to a provider, restore Automatic, or choose/clear a primary contact item. Paid provider selection requires confirm=true; inspect sources and the lookup plan first.

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, openWorldHint=true and idempotentHint=false, so the safety profile is known; the description adds genuinely new context by disclosing that provider selection is a paid action requiring explicit user approval via confirm=true. It stops short of saying what state is lost when restoring Automatic or clearing a primary contact, which matters for a destructive tool.

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 tight sentences: the first enumerates the modes, the second front-loads the two constraints (approval and prior inspection). Dense but every clause carries information; the compressed enumeration of actions is slightly harder to scan than a list.

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?

For a four-variant destructive mutation with no output schema, the description covers the mode selection and approval gate but leaves the concurrency guard, fallback behavior, and lock semantics undocumented. An agent can pick the right action but may not invoke the variants safely in edge cases.

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 high (confirm even carries its own warning), so the baseline is 3. The description maps the four actions onto schema consts and explains the confirm gate, but says nothing about lock, allow_fallback, observation_id, provider_key, item_key, or the optimistic-concurrency field expected_current_selection_id.

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?

Names the four concrete operations precisely – select a stored observation, lock to a provider, restore Automatic (reset), and set/clear a primary contact item – which maps one-to-one onto the schema's action constants. An agent can tell this is the field-source selection tool, though it never explicitly contrasts itself with siblings like spur_get_field_sources.

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?

Provides a real prerequisite: 'inspect sources and the lookup plan first', which routes the agent to the discovery/planning siblings before calling. It also gates the provider path on confirm=true after explicit user approval, but gives no when-not guidance (e.g., when to use refresh_property_data instead) or note on which action to prefer.

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