Skip to main content
Glama

get_suprsend_object_preferences

Read-onlyDestructiveIdempotent

Read an object's notification preferences by category, with optional per-channel overrides. Use before updating preferences or checking delivery permissions.

Instructions

Read an object's category-level notification preferences and (optionally) per-channel overrides.

When to use:

  • Before update_suprsend_category_preference_object, to read current state.

  • Before sending to an object, to check delivery permission.

When NOT to use:

  • For the object's identity or channels — use get_suprsend_object.

  • For users — use get_suprsend_user_preferences.

Returns: the object's preference tree. Pass category to scope to one preference; omit for the full tree. Set channel_preferences=true to include per-channel overrides.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoThe category_slug of the object to get preferences from, if not provided, it will get all the preferences for the object.
channel_preferencesNoset this to true to get all the channel preferences for the object.
object_idYesThe object_id of the object to get preferences from.
object_typeYesThe object_type of the object to get preferences from.
workspaceNoSuprSend workspace to get the user from.
Behavior3/5

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

Description accurately describes read-only behavior, but adds little beyond annotations; annotations already convey readOnlyHint and idempotentHint. The description is consistent but not richer.

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?

Well-structured with sections, front-loaded, every sentence adds value without redundancy.

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?

Explains return value and parameter usage, but lacks detail on response format; adequate given no output schema.

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 coverage is 100%, but description clarifies parameter usage (category scoping, channel_preferences toggle) beyond schema descriptions.

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?

Description clearly states verb 'Read' and resource 'object's category-level notification preferences', and distinguishes from siblings like get_suprsend_object and get_suprsend_user_preferences.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'When to use' and 'When NOT to use' sections with specific use cases and alternative tool references.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/suprsend/cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server