Skip to main content
Glama
mefcs-mcp

mefcs-mcp

by cayocan

TONE3000 login status

tone3000_auth_status

Checks how the MCP server authenticates with TONE3000 and reports status, helping users verify connectivity and troubleshoot authentication problems.

Instructions

Show how the MCP authenticates with TONE3000.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about whether this performs a network round-trip, whether it errors when unauthenticated, or whether the returned data includes sensitive credential/token details. Only a weak read-only implication can be drawn from the verb "show."

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

Conciseness4/5

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

A single short sentence with no filler, front-loaded with the verb. It is efficient, though the brevity borders on under-specification rather than tight writing.

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

Completeness2/5

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

With no output schema, the description is the only place an agent could learn what this returns — authenticated/unauthenticated state, account identity, token expiry, or error behavior — and it supplies none of that. For a status tool whose entire value is its return value, this is a meaningful gap.

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 empty schema is fully consistent with the description.

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 says it will "show how the MCP authenticates with TONE3000," which reads more like an explanation of the auth mechanism than a report of the current login state. The title ("login status") clarifies intent, but the description alone does not cleanly state that it returns the present authentication status, and it draws no boundary against tone3000_login_start, tone3000_login_finish, or tone3000_set_credentials.

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 the login_start/login_finish pair or set_credentials, and no stated precondition such as "call before other tools to check whether login is required." The agent must infer the call site entirely from the sibling names.

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