Skip to main content
Glama

mcpsense_status

Read-only

Check the running CLI/MCP version, approved project root, startup permissions, and available scan modes before inspecting MCP configurations.

Instructions

Start here. Get the running CLI/MCP version, approved project root, startup permissions and available scan modes. The MCP server ships with the same engine and version as the CLI.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description's added value is the disclosure of what state is surfaced: version, approved project root, startup permissions, scan modes. The note that the MCP server shares the CLI's engine and version is genuine context an agent cannot get from structured fields, though nothing is said about caching or freshness of that status.

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?

Two short sentences with the actionable imperative front-loaded ('Start here'), followed by a single supporting fact. Nothing is redundant with the name or the annotations, and every clause carries information.

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

Completeness5/5

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

With no input parameters and no output schema, the description carries the burden of describing the return payload, and it does so by naming the four categories of status returned. For a simple read-only status probe, nothing an agent needs in order to call it correctly is missing.

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 the baseline is 4; there are no argument semantics to explain. The description correctly avoids inventing input details and instead spends its words on the outputs.

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

Purpose5/5

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

The description states a concrete verb-and-resource pair ('Get the running CLI/MCP version, approved project root, startup permissions and available scan modes') and enumerates exactly what comes back. 'Start here' plus the mention of scan modes positions it against siblings like mcpsense_scan and mcpsense_verify without ambiguity about what this tool itself does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Start here' is an explicit invocation directive, telling the agent to call this before anything else. It does not name when-not-to-use conditions or call out specific alternatives, but for a zero-parameter entry-point status tool the sequencing guidance is the relevant guidance and it is unambiguous.

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