Skip to main content
Glama

get_mcp_capabilities

Read-onlyIdempotent

Show this token's scopes and the scopes the server currently offers, how interviews are funded (on the website, a platform-funded private interview costs one universal credit, or the Unlimited plan (the user's own Gemini API key) uses no credit), and whether this account can create new scenarios now: that needs purchased interview credits or an active Unlimited plan, while saved scenarios stay usable. To start a mock interview, use the start_mock_interview prompt or prepare_mock_interview, which returns the website setup link. A scope does not prove Question Bank entitlement.

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_mcp_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
tokenScopesYes
websiteOriginYes
availableScopesYes
interviewLocationYes
scenarioCreationAllowedYes
privateInterviewCreditCostYes
privateInterviewCreditTypeYes
scenarioCreationRequirementYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description goes beyond that with real behavioral context: credit accounting rules, that an active Unlimited plan or purchased credits gate scenario creation, that saved scenarios remain usable without them, and the caveat that a scope does not prove Question Bank entitlement. Only the exact output shape is left unaddressed, which the output schema covers.

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?

Information density is high and nothing is pure filler, but the first sentence is a run-on with a nested parenthetical about universal credits and the Unlimited plan that is hard to parse in one pass. The routing sentence and the Question Bank caveat are well placed; splitting the opening into two shorter statements would improve scanability without losing content.

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 zero-parameter, read-only diagnostic tool with an output schema, this covers the questions an agent would need answered to interpret the result: what scopes mean, how funding works, and whether creation is currently permitted plus the distinct caveat about Question Bank entitlement. Return-value formatting is correctly delegated to the 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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline applies. The description correctly does not waste space on 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 names concrete resources it reports on: token scopes, server-offered scopes, interview funding model, and whether the account can create new scenarios. The specific verb is weaker ('show') and the content is bundled into one long sentence, but the scope of the tool is unambiguous and clearly differs from siblings like get_account_summary or get_progress_summary.

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 explicitly routes the agent away for the main adjacent task: 'To start a mock interview, use the start_mock_interview prompt or prepare_mock_interview, which returns the website setup link.' That is a genuine alternative-plus-condition statement. It does not, however, say when this tool itself should be called (e.g. before attempting scenario creation), leaving that implied.

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