Skip to main content
Glama

status

Read-only

Check dry-run or live mode, login state, and active negotiation rules before searching listings, messaging sellers, or negotiating a purchase price.

Instructions

Dry run or live, login state and the negotiation rules in force.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, so the safety profile is covered. The description adds that status covers dry-run/live mode, login state, and negotiation rules, which is useful behavioral context, but it does not describe return format or whether values reflect the current session versus static configuration.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is very short and contains no filler, but the telegraphic comma-separated fragment is not front-loaded with a clear action and forces interpretation. It is concise at the cost of clarity.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read-only status tool, the definition covers the major status categories, but with no output schema it should say more about what is returned and how to interpret dry-run/live or negotiation rules. It is minimally adequate rather than complete.

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 has zero input parameters, so there is no parameter semantics for the description to supplement. The empty schema is consistent with a status check.

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

Purpose3/5

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

The description indicates a diagnostic status resource but does not use a clear verb such as 'returns' and its phrasing is a fragment. It identifies the status dimensions (dry-run/live mode, login state, negotiation rules), which distinguishes it somewhat from negotiation CRUD siblings, but an agent still has to infer that this is a status-reporting tool.

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?

No explicit when-to-use guidance, prerequisites, or alternatives are provided; siblings like get_negotiation are not referenced. The agent can infer it is for checking current environment, authentication, and configuration state, but that is not stated.

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