Skip to main content
Glama

status

Shows all configured Lagsmith rules, what each rule is doing, and whether the proxy is currently running.

Instructions

Show every rule, what it's doing, and whether Lagsmith's proxy is running.

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.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does usefully disclose the return content (all rules, their activity, proxy running state), which is more than a tautology. However, it never states that the call is read-only with no side effects, nor anything about ordering, size, or freshness of the reported state — material for a zero-annotation tool.

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 three things it returns are enumerated compactly. Nothing could be removed without losing content.

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-param, no-output-schema diagnostic, the description covers the essential return content, so an agent knows what it will get back. It falls short only on safety/read-only framing and on scoping what "rules" refers to, which matter little given the tool's simplicity.

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 no parameter semantics to explain; the baseline for a no-param tool applies. The description correctly implies the call needs no input to produce a full status snapshot.

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 names a verb ("show") and two concrete payloads: every rule with its current activity, and whether Lagsmith's proxy is running. That makes the diagnostic/status intent recognizable, but "every rule" is underspecified (rules of what domain?) and nothing distinguishes it from status-like siblings such as get_requests or clear_endpoints.

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 guidance on when to call this versus alternatives; the description never mentions any sibling or condition for selection. An agent must infer that this is the first-stop diagnostic tool from the word "status" and the description alone.

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