Skip to main content
Glama

AceRound AI Interview Copilot

list_plans

Read-only

List the plans on sale, with prices and what each one includes.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

The annotations already establish that this is a read-only, non-destructive, closed-world operation, so the safety profile is covered. The description adds value beyond them by disclosing what the results contain (prices and per-plan inclusions), which matters because there is no output schema. It does not mention ordering, pagination, or whether inactive plans are excluded, which keeps it from a 5.

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

Conciseness5/5

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

A single sentence with no filler: the action comes first and the return content follows immediately. Nothing could be removed without losing information, and there is no restating of the tool name as a separate clause.

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 listing tool with no output schema, the description needs to convey roughly what comes back, and it does so at a high level (plans, prices, inclusions). It falls slightly short of fully substituting for an output schema, since field names and result shape remain unspecified, but the remaining gap is minor given the tool's simplicity.

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 no parameters, so there is nothing for the description to disambiguate beyond the empty schema; the baseline for a zero-parameter tool applies. The description correctly does not invent filtering options that the schema does not support.

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 gives a specific verb and resource ('List the plans on sale') and adds the scope of returned data ('prices and what each one includes'), which separates it from the many sibling list_* tools covering resumes, interviews, and knowledge bases. It stops short of naming an alternative or stating a boundary case, so it is clear but not fully differentiated.

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: an agent can infer this is the tool to call when it needs plan or pricing information, but there is no explicit when-to-use statement, no prerequisites, and no pointer to a sibling such as a subscription or order-status tool for follow-up actions. For a zero-parameter list tool this is the minimum viable level.

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