Skip to main content
Glama

AceRound AI Interview Copilot

get_auto_apply_quota

Read-only

Show Auto Apply credits: applications left, when unlimited ends, and any wait required before the next one. (Requires the user's sign-in with scope job_applications: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_auto_apply_quota"
  }
}

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, and closed-world, and the description adds genuinely new context: the required sign-in and the job_applications:read scope. It also discloses the shape of the data (remaining credits, unlimited expiry, cooldown), though it does not say whether quota is per-account or per-profile.

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?

Two short sentences, zero padding, with the returned data front-loaded and the authorization requirement placed in a trailing parenthetical where it does not obstruct the main purpose.

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 with no output schema, the description covers the return fields and the auth requirement, which is most of what an agent needs. The only gap is the absence of scoping detail (which account/profile the quota applies to).

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 schema semantics for the description to supplement; the baseline for a no-param tool applies. Nothing in the description misrepresents the parameter-less nature of the call.

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 a specific verb ('Show') and resource ('Auto Apply credits') and enumerates the exact data returned: applications left, unlimited-end timing, and next-application wait. It does not explicitly contrast with the sibling buy_auto_apply_credits, so it stops short of a 5.

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 a pre-flight check before applying or before purchasing credits, but there is no explicit 'use this when' or 'use buy_auto_apply_credits instead when' statement. No exclusions or prerequisites beyond auth are stated.

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