Skip to main content
Glama

Status da conexão

designeer_status

Determines whether the MCP is in live API mode or offline static-index mode and reports how many items the index contains.

Instructions

Diz se o MCP está em modo live (API completa) ou offline (índice estático), e quantos itens o índice tem.

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": "designeer_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?

With no annotations at all, the description carries the full disclosure burden. It does add real value by revealing a degraded-mode distinction (live full API vs offline static index) that affects how much an agent should trust other tools' results, but it says nothing about cost, prerequisites, or what the response looks like.

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 sentence with no filler; the two pieces of information returned (mode and index size) are front-loaded and stated in one pass. 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 trivial zero-parameter status tool with no output schema, the description conveys both return concepts and the important live/offline distinction. Only the concrete response shape is unspecified, which is a minor gap for a tool of this 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 the baseline is 4 and there is nothing for the description to clarify. No parameter meaning is missing or misrepresented.

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 names a specific reporting action and its two subjects: whether the MCP is in live mode (full API) or offline (static index), plus the number of items in the index. That makes it clearly a diagnostics/status tool, distinct from the data-retrieval siblings (browse, get, search), though it never explicitly contrasts itself with them.

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?

No explicit when-to-use or when-not-to-use guidance is given, no statement such as 'call this before search to confirm live data is available'. The diagnostic intent is implied strongly enough by the content that an agent can infer the use case, but it must do the inferring itself.

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