Skip to main content
Glama

AceRound AI Interview Copilot

get_prompt_presets

Read-only

Prompt studio: see the state of the interview and exam prompts — what is in effect now, the user’s saved custom prompt, the official version and whether it has been updated, each built-in style, and built-in exam questions for trial runs. Returns an overview with lengths; pass show to read one text in full. (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_prompt_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoInterview language to render for; defaults to the saved one
showNoWhich text to return in full: current / saved / official / style:<value>

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 openWorldHint=false, so the safety profile is covered. The description adds value beyond that by stating the auth prerequisite (user sign-in with scope interviews:read) and by disclosing the two response modes: a summary overview with lengths by default, or one full text when 'show' is supplied.

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?

The core capability and the 'show' behavior are front-loaded, and the auth note is appropriately parenthesized at the end. The first sentence is long and list-heavy with em-dashes, making it dense to parse, but no sentence is redundant.

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?

For a read-only, two-parameter tool with a fully documented schema and no output schema, the description covers purpose, the two response modes, and the auth requirement. It lacks only an explicit pointer to sibling tools for the mutation/trial steps that would naturally follow an inspection.

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

Parameters3/5

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

Schema description coverage is 100% and both parameters carry enum values with their own descriptions, so the baseline is 3. The description adds a little on top by clarifying that omitting 'show' yields an overview with lengths rather than full text, but it says nothing about the 'lang' parameter's rendering behavior.

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 resource ('Prompt studio') and enumerates exactly what state is returned: current prompt in effect, saved custom prompt, official version plus update status, built-in styles, and built-in exam questions. It reads clearly as a read-only inspection tool, implicitly separating it from siblings like rewrite_prompt, save_custom_prompt and run_prompt_trial, but it never names those alternatives 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?

It gives one concrete usage rule: the default call returns an overview with lengths, and you pass 'show' to read a single text in full. That is enough to pick the right call shape, but there is no explicit statement of when to reach for this tool versus the rewrite/save/trial siblings, so the agent must infer the workflow position.

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