Skip to main content
Glama

Manage source preferences

spur_manage_data_preferences

Get, save, or delete persistent source preferences. Saving preferences makes no paid lookup. Read the segment/catalog first.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the description does not need to restate mutability. It adds genuine context beyond them: that saving is not a paid lookup and that catalog/segment reading should precede configuration. There is mild tension between a "delete" action and destructiveHint=false that the description does not reconcile, and it does not say whether saved rules override existing ones.

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?

Three short, front-loaded sentences with no filler; the action list comes first and prerequisites last. The sentence "Saving preferences makes no paid lookup" is slightly compressed and requires inference, but nothing is wasted.

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 configuration tool with a fully documented nested schema and no output schema, the description covers the essentials: actions, cost profile, and prerequisite reading. The remaining gap is conceptual — it never explains what a "source preference" rule actually controls (provider ordering, freshness, blocking) — which an agent would need to compose valid rules.

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% and the oneOf branches fully document action, rules, rule fields and rule_id, so the schema carries the load. The description only echoes the three action values and adds nothing about what mode values (automatic/preferred/locked) or target_type actually mean. Baseline 3 is appropriate.

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 opens with a specific verb set and resource: "Get, save, or delete persistent source preferences." An agent immediately knows the three actions and the object being managed, and the action constants in the schema confirm the mapping. It does not name a specific sibling tool, so it falls short of 5, but the resource is distinct enough within the catalog.

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?

"Read the segment/catalog first" gives an ordering prerequisite, and noting that saving makes no paid lookup tells the agent saving is cheap relative to job-running tools. However, there is no explicit guidance on when to choose this over catalog/search tools, no statement of what happens if preferences already exist, and no exclusion conditions.

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