Skip to main content
Glama

status

Read-onlyIdempotent

Checks credential vault state, SIGAA session state, rate-limit counters, and active tool profile.

Instructions

Retorna estado do cofre de credenciais, estado da sessão no SIGAA, contadores de limite de taxa e perfil de ferramentas ativo.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds which state categories are surfaced, but says nothing about whether it performs a live SIGAA network round-trip (relevant for latency/rate-limit behavior) or whether it requires an authenticated session.

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?

A single dense sentence with no filler, and the resource list is front-loaded after the verb. It is appropriately sized for a zero-argument status tool, though the flat enumeration offers no structural prioritization of which state matters most.

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?

An output schema exists, so return-value detail need not be repeated, and the annotations cover the safety profile; the description fills the remaining gap by naming the four state domains. The only real omission is the lack of a pointer distinguishing this from 'diagnostico' and no note on whether the call hits the network.

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 nothing for the description to disambiguate; baseline 4 applies. The enumeration of returned state categories is a small bonus but belongs to the output contract already covered by the output schema.

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 uses a specific verb ('Retorna') and enumerates the exact resources reported: credential vault state, SIGAA session state, rate-limit counters, and the active tool profile. That is far more than a restatement of the name 'status', though it does not distinguish this from the sibling 'diagnostico', which an agent could easily confuse with it.

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; the description only lists outputs. With a sibling named 'diagnostico' present, the absence of any routing signal leaves the agent to infer that this is a health/state check rather than a diagnostic run.

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