Skip to main content
Glama

ResumeVsJob Batch

Credits left on a license key

credits_left
Read-only

Shows how many resume checks are left on a license key.

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

Input Schema

NameRequiredDescriptionDefault
license_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds meaningful domain context about what the returned number represents (remaining resume checks), but says nothing about behavior when license_key is omitted (it is not required), nor about invalid/expired keys.

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?

One short, front-loaded sentence with no filler, and the key concept (remaining checks) is placed early. Its brevity borders on under-specification rather than wastefulness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only, single-parameter tool whose safety profile is fully covered by annotations, the description is close to sufficient and implies a numeric count return. The remaining gaps — behavior with a missing or invalid key and the response shape (no output schema exists) — keep it at adequate rather than complete.

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 0%, so the description must carry the load; it does tie the single parameter to the license key being queried. However, it gives no format, no hint about the optional/required status of license_key, and no indication of what happens if the key is not supplied.

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 states a specific verb-and-resource pair ("shows how many resume checks are left") plus the scoping key ("on a license key"), so the agent knows this is a quota-lookup rather than the actual resume check. It does not explicitly contrast itself with the sibling check_resumes, leaving that distinction to inference.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. At best an agent can infer this is a pre-flight quota check before calling check_resumes, but that is left entirely implicit.

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