Twelfth

Get preferences

twelfth_get_preferences

Read-onlyIdempotent

Read stored preference values and the keys this connection may read at user, organization or membership scope. Use it for defaults such as cover targets and display choices. For Twelfth staff with workspace owner/admin access, organization scope also returns the managed chat runtime policy and available models. Those staff with Allow changes can use twelfth_update_agent_policy for runtime settings. Integrations and category remits have their own tools (twelfth_list_integration_guides, twelfth_list_category_settings); personal and membership scopes need a person's OAuth connection.

Input Schema

Name	Required	Description	Default
`scope`	Yes	Whose preferences to read: user (your account), organization (the workspace) or membership (your role in this workspace). A workspace key can read organization only.

Output Schema

Name	Required	Description
`keys`	Yes	Preference keys this connection can read at this scope.
`scope`	Yes
`values`	Yes	Stored values by preference key.
`settings`	Yes
`agentPolicy`	No	Effective chat runtime, overrides, available model IDs and this connection's write eligibility.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 15, 2026

addedOutput schema / properties / agentPolicy

Added value: +{
+  "additionalProperties": {},
+  "description": "Effective chat runtime, overrides, available model IDs and this connection's write eligibility.",
+  "type": "object"
+}

removedOutput schema / properties / settings / items / properties / canWriteViaMcp / const
```
Removed value: -false
```

Changed1 schema field changedOct 4, 2026

changedOutput schema / properties / settings / items / required

Previous value: -[
-  "key",
-  "value",
-  "hasValue",
-  "roleAllowsEditInApp",
-  "canWriteViaMcp",
-  "editPolicy"
-]New value: +[
+  "key",
+  "hasValue",
+  "roleAllowsEditInApp",
+  "canWriteViaMcp",
+  "editPolicy"
+]

First observedOct 4, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), but the description adds real behavioral context: organization scope returns managed chat runtime policy and available models, but only for staff with workspace owner/admin access, and write access depends on 'Allow changes'. It stops short of describing return shape, though an output schema exists.

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?

Front-loaded with the core action, then progressively adds scope behavior, alternatives, and auth caveats; every sentence carries information. Slightly dense with parenthetical tool references, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-enum, read-only tool with an output schema, the description covers purpose, scope semantics, permission gating, and sibling alternatives. Nothing needed to select or invoke it correctly is missing.

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% and the enum values are documented in the schema, so the baseline is 3. The description goes further by explaining what each scope yields and the access rule ('A workspace key can read organization only'), which adds meaning beyond the schema text.

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?

States a specific verb and resource ('Read stored preference values and the keys this connection may read') and immediately bounds it to user/organization/membership scope. It explicitly separates itself from nearby siblings (integrations, category remits) by naming the tools that handle those.

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?

Gives concrete when-to-use context ('defaults such as cover targets and display choices') and routes alternative needs explicitly: twelfth_update_agent_policy for runtime settings, twelfth_list_integration_guides / twelfth_list_category_settings for their domains, and OAuth connection for personal scopes. Both the positive and negative cases are covered.

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

All Twelfth tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.