Skip to main content
Glama

Get account settings

clipember_get_account_settings
Read-onlyIdempotent

Get the connected ClipEmber account's name, email, current billing plan, whether "publish only approved" is on (shared posts wait for the client's approval), whether "members' posts need approval" is on (membersNeedApproval; yourPostsNeedApproval says whether it applies to you), and the time zone the calendar and emails use (timezone; null = automatic, the browser's zone in timezoneDetected), the clock they show (timeFormat: 12h or 24h; null = automatic, the browser's habit in timeFormatDetected) and the first day of the calendar week (weekStart: sunday or monday). Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clipember_get_account_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the trailing "Read-only." repeats structured data. The real value is the field-level semantics (membersNeedApproval vs yourPostsNeedApproval, null=automatic, timezoneDetected/timeFormatDetected fallbacks), which is substantial behavioral context beyond annotations, though it describes output shape more than tool behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sprawling sentence stitched together with parentheticals and semicolons, which makes it dense to parse despite containing little filler. Front-loading the primary fields (name, email, plan) is good, but the approval/timezone/format/week-start clauses could be broken out for readability.

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?

With no output schema, field semantics are the only documentation of return values, and the description covers them thoroughly, including null/automatic fallbacks. It is close to complete for a zero-parameter read tool; only explicit routing to the update sibling 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The parenthetical explanations of nullable fields and *Detected companions correctly attach meaning to values rather than to inputs.

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+resource ("Get the connected ClipEmber account's name, email, current billing plan...") and enumerates the exact settings returned, so the purpose is unmistakable. It does not, however, distinguish itself from the sibling clipember_update_account_settings or mention that reads are non-mutating counterparts.

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?

Usage is only implied by the name and the field list; there is no explicit "use this when..." guidance or pointer to update_account_settings for changing values. An agent can infer the read use case, but nothing tells it what to do instead when it needs to write.

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