Skip to main content
Glama

Account and plan

get_account
Read-onlyIdempotent

Use this when the person asks which CVEmber account is connected or whether they can download. Returns the connected account as a masked email, whether PDF download is available now, and what this connection may do.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior. The description adds value beyond that by disclosing the return shape — masked email (privacy-preserving), current download eligibility, and a permission scope — so the agent knows what it can learn without a trial call.

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 sentences, zero waste: the trigger condition is front-loaded and the return contents follow immediately. Nothing is repeated from the annotations or title.

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?

With no output schema, the description carries the burden of explaining return values, and it does so at a useful level of abstraction. The phrase 'what this connection may do' is slightly open-ended about the exact scope fields returned, which keeps it from a 5 for a zero-argument tool whose whole value is its response.

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 the baseline is 4 and there is nothing for the description to disambiguate. No parameter semantics are needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (the connected CVEmber account) and states exactly what is returned: a masked email, current PDF-download availability, and what the connection is permitted to do. It is clearly distinct from the resume-oriented siblings, none of which touch account or plan state.

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 gives an explicit trigger condition — 'when the person asks which CVEmber account is connected or whether they can download' — which is a clear context for selection. It stops short of stating when not to use it or naming an alternative, but no sibling plausibly overlaps with account lookup.

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