Skip to main content
Glama

Get sources for one field

spur_get_field_sources
Read-onlyIdempotent

Show every stored value for one field of a saved property, with its provider and date, plus which other providers could supply it and how many data credits a lookup uses. Free. Use this to answer "where did this number come from?" or before switching provider.

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": {
      "property_id": "<property_id>",
      "data_point": "<data_point>"
    },
    "name": "spur_get_field_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
data_pointYesData point key, e.g. physical.bedrooms or financial.estimated_equity. Call spur_list_data_providers to see keys.
property_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds the notable behavioral fact that the call is free (zero credits) while reporting credit cost of alternative lookups, but says nothing about return shape, volume of values, or failure modes.

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 dense sentences, front-loaded with the primary behavior, then the cost note, then the use case. No filler; every clause carries 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?

No output schema exists, and the description does the work of describing return contents (stored value, provider, date, alternative providers, credit cost). Combined with the safety annotations, an agent has enough to call it correctly, with property_id semantics the only real gap.

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 50%: data_point is fully described with a pattern and a pointer to spur_list_data_providers, but property_id has no description. The description's "one field of a saved property" loosely maps to both parameters without adding format or constraint detail, so it neither compensates for nor compounds the gap.

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 and resource: show every stored value for one field of a saved property, including provider, date, alternative providers, and credit cost. Scope (single field) implicitly separates it from the property-level sibling spur_get_property_sources, though no sibling is named explicitly.

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?

Gives concrete trigger conditions: answer "where did this number come from?" or check before switching provider. Clear usage context, but no explicit when-not guidance or named alternative tool for the property-wide case.

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