Skip to main content
Glama

Add properties or import mapped rows

spur_add_manual_properties

Preview a typed address for free, create a property with manually supplied facts/contacts, or import up to 100 mapped rows from CSV. No provider lookup. CSV rows use the documented address/details/owner shape; do not invent missing data.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive, non-idempotent, closed-world mutation, and the description adds real context beyond that: preview costs nothing, no external provider call occurs, imports are capped at 100 rows, and callers must not fabricate missing fields. It does not describe what happens on partial import failure or duplicate addresses, which is the main remaining gap.

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 compact sentences, front-loaded with the three modes, followed by the negative constraint and the CSV shape warning. No filler, and the most decision-relevant information comes first.

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 three-mode mutation tool with no output schema and a large nested oneOf input, the description covers modes, cost implications, row limits, and data-shape rules well. What is missing is return behavior, such as what a preview yields or whether import reports per-row failures, which matters for an agent planning follow-up calls.

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 reported at 100%, so the schema already carries the structural burden, and the context signals list zero top-level parameters despite the oneOf branches. The description adds some meaning by naming the address/details/owner row shape and instructing against inventing missing data, but it does not explain action semantics such as when list_id matters or how file_name is used.

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?

The description names three distinct operations with concrete verbs and resources: preview a typed address, create a property with supplied facts/contacts, and import up to 100 mapped CSV rows. Each mode maps cleanly to a branch of the input schema's oneOf, so an agent can identify which action to take 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?

It clearly states the boundary condition 'No provider lookup', which tells the agent this tool is for user-supplied or CSV data rather than enrichment lookups. It also flags the free preview path, guiding cheap validation before a paid create. It stops short of naming a sibling to use when provider lookup or enrichment is actually wanted.

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