Skip to main content
Glama

get_crypto_security_status

Inspect active anti-drainer guards, single and daily spending caps, and emergency lockdown status to verify wallet security protections before DeFi interactions.

Instructions

Inspect active Anti-Drainer guards, single/daily spending caps, and emergency lockdown status.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and "Inspect" plus "status" implies a non-mutating read, which is a useful signal. It discloses the scope of what is examined (guards, caps, lockdown state) but says nothing about whether the call requires authorization, whether it is global or per-wallet, or what the response looks like. For a zero-parameter read the gap is modest but real.

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 zero filler, front-loaded with the verb and followed by the three concrete facets inspected. Every clause adds information and nothing is repeated from the name 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?

For a zero-parameter, annotation-free status tool the description covers the essential question of what is inspected, which is the main thing an agent needs. The remaining gap is return-shape ambiguity: there is no output schema and the description does not indicate whether results are global or scoped, leaving the agent to discover the structure on first call.

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 at all, so there is no parameter semantics to explain and the baseline of 4 applies. Nothing in the description misleads about inputs, and the absence of arguments is consistent with a global status read.

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 opens with a specific verb ("Inspect") and names the exact resource facets returned: Anti-Drainer guards, single/daily spending caps, and emergency lockdown status. An agent can immediately tell this is a read of security configuration rather than a transfer or approval action. It stops short of naming any sibling explicitly, so differentiation is by implication from the enumerated facets rather than by direct contrast.

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?

There is no explicit when-to-use statement, no exclusion, and no mention of prerequisites such as authentication or wallet scoping. Usage is only implied: the facets listed (spending caps, lockdown) suggest a pre-transfer safety check, but the agent must infer that on its own. No alternative tool is named or ruled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.