Skip to main content
Glama

Read personalization

spur_get_personalization
Read-onlyIdempotent

Read the live angle/goal/tone/token catalog, current settings, a list's review queue, a saved line, or angle performance. Free. New merge fields include ai_opener, ai_reason, ai_cta, ai_ps, ai_subject, ai_first_name and ai_custom_.

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 declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new decision-relevant context beyond that: the call is free (no credit cost), and the catalog carries 'new' merge fields, which matters to an agent deciding whether to refresh state. It does not explain per-section behavior, but the bar is lower given full annotation coverage.

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, front-loaded with the capability enumeration, with no filler. The trailing merge-field sentence is slightly ad-like but still conveys catalog content, so it earns its place.

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?

There is no output schema, so the description bears the burden of describing return values, and it only gestures at them ('catalog', 'settings', 'angle performance') without stating shape or volume for any section. For a multi-mode, oneOf-discriminated read tool, that leaves a real gap even though annotations cover the safety profile.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description earns above baseline by expanding the terse enum values: 'catalog', 'settings', 'list' (review queue), 'record' (a saved line), and 'performance' (angle performance). That translation from opaque discriminators to business meaning is real added value. It does not cover the optional 'days' or 'personalization_id' arguments.

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 gives a precise verb ('Read') plus an enumerated set of resources: catalog, settings, a list's review queue, a saved line, and angle performance. These map cleanly onto the five schema sections, so an agent can tell it apart from spurious write siblings like spur_review_personalization or spur_update_personalization_settings. It stops short of naming a sibling alternative explicitly.

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-oriented phrasing implies retrieval rather than mutation, and 'Free' signals it is cheap to call speculatively, which is useful usage context. However, it never states when to prefer this over siblings such as spur_generate_personalization or spur_review_personalization, and gives no exclusions or prerequisites.

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