Skip to main content
Glama

My account security status

security_status_get
Read-onlyIdempotent

A snapshot of your Barmaan account security: whether a password is set and when it last changed, whether your contact address is verified, whether Telegram is linked, how many sign-in sessions and connected AI apps are active, and any alerts. Facts only, no secrets. Changing password or closing sessions is only possible on the website (Account, Security).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and closed-world, so the safety profile is supplied. The description adds genuinely new behavior context: 'Facts only, no secrets' sets expectations about what is and is not exposed, and the explicit statement that mutations are impossible here prevents an agent from attempting a write through this tool. It does not discuss caching or freshness of the snapshot, which is the remaining gap.

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?

Front-loaded with the snapshot summary, then the fields, then the constraints. The field enumeration is long but each item maps to a distinct fact an agent would report, so it earns its place. A single sentence carries the whole payload without preamble or redundant restatement of the title.

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

Completeness5/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 bears the burden of describing return content, and it does so field by field. Combined with the zero-parameter schema and read-only annotations, an agent has everything needed to decide to call it and to interpret the result without guessing.

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 the baseline is 4; there is no argument syntax that needs explaining. The description correctly avoids inventing parameter talk and instead spends its words on what the zero-argument call returns.

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?

Names a specific resource (Barmaan account security status) and enumerates exactly what the snapshot covers: password presence/change date, contact verification, Telegram link, session and AI-app counts, alerts. An agent can tell this is an aggregate overview rather than an event or session listing, which is the key distinction from the activity/session siblings.

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?

Establishes clear usage context: this is a read-only snapshot and any remediation (changing password, closing sessions) must happen on the website under Account, Security. That excludes an entire class of misinvocations. It stops short of naming security_sessions_list or security_activity_list as the drill-down alternatives when the counts raise a question, so the routing guidance is incomplete rather than absent.

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