Skip to main content
Glama

Portward account status

account_status
Read-only

Check whether this computer is signed in to a Portward account and identify which user is authenticated, so you can verify access before running queries.

Instructions

Whether this computer is signed in to the user's Portward account, and as whom.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuine context by scoping the answer to "this computer" (local machine state, not a server-side account listing) and by promising an identity, not just a boolean. It says nothing about what happens when no one is signed in, which is the main behavioral unknown for a status check.

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 front-loaded sentence with no filler; the two facts an agent needs (is it signed in, and as whom) arrive immediately. Nothing is repeated from the title or annotations.

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 read tool with no output schema, the description covers what is being reported and the scope of the report. The only shortfall is the unsigned-in case, where an agent cannot tell whether to expect a null, an error, or a signed-out value.

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 and the baseline of 4 applies. The schema and description are consistent in presenting a no-argument call.

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 sentence names the resource (the user's Portward account) and the exact information returned: sign-in state plus identity ("as whom"). That is specific enough to separate it from the mutating siblings account_sign_in, account_sign_out, and account_delete, though the read-only contrast is left implicit rather than stated.

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?

Usage is only implied — an agent can infer this is the check-before-acting tool for auth state, but the description never says when to call it, nor points to account_sign_in as the remedy when the answer is negative. No explicit alternatives or exclusions are given.

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