Skip to main content
Glama

AceRound AI Interview Copilot

get_settings

Read-only

Read the user’s cloud-saved settings: interview preferences (language, translation, answer style, default knowledge bases, replay, web search…), exam answer customization (answer language, programming language, code style, code mode, extra requirements, quick prompts) and desktop client settings (hotkeys, overlay style, modes, auto-answer…). Custom prompts are shown as lengths only; read them with get_prompt_presets. (Requires the user's sign-in with scope interviews:read.)

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": "get_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and closed-world behavior, so the safety profile is covered. The description adds genuinely non-schema information: the required auth scope (interviews:read) and the important data-shaping quirk that custom prompts come back as lengths only, not content. It stops short of describing response shape or size, which is the only remaining gap.

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?

A single front-loaded sentence states the action and inventory, followed by two short clauses covering the prompt-text exception and the auth requirement. It is dense but every clause carries unique information; the long parenthetical enumerations are slightly heavy but they are what makes the return contents predictable.

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 zero-parameter, read-only getter with no output schema, an agent needs to know what comes back, what is withheld, and what credentials are required — all three are present. Nothing material is missing before a correct invocation.

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 input schema has zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies a no-argument call by listing only what is returned.

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?

The description opens with a specific verb+resource ("Read the user's cloud-saved settings") and then enumerates the three concrete domains returned: interview preferences, exam answer customization, and desktop client settings. It also carves out what it does NOT return ("Custom prompts are shown as lengths only"), which lets an agent distinguish it from get_prompt_presets without opening either schema.

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

Usage Guidelines4/5

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

It gives an explicit routing rule for the one ambiguous case: to read actual custom prompt text, use get_prompt_presets instead of this tool. It does not mention that writing settings is handled elsewhere (e.g. update_client_settings) or state any preconditions beyond sign-in, so the guidance is clear but not exhaustive over the sibling set.

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