Skip to main content
Glama
mefcs-mcp

mefcs-mcp

by cayocan

TONE3000 login (finish)

tone3000_login_finish

Waits for the user to approve a TONE3000 device code, polling for up to 60 seconds per call to complete login.

Instructions

Wait for the user to approve the device code (up to 60 s per call).

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_login_finish"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 behavioral burden. It usefully discloses that the call blocks up to 60 seconds and can be called repeatedly, but it omits what happens on timeout and whether approval yields credentials.

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 redundant wording. It is appropriately sized for a zero-parameter tool, though the terseness contributes to the guidance gaps.

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?

The tool itself is simple, but without an output schema the description should explain the outcome of a successful or timed-out finish call. It also does not connect the finish step to tone3000_login_start or tone3000_auth_status.

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?

There are zero parameters and schema description coverage is 100%, so there is no parameter semantics to add beyond the baseline. A 4 is appropriate for a no-parameter tool.

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 action, waiting for approval of a device code, and the title frames it as the finish step of login. It does not explicitly distinguish this from tone3000_auth_status or tone3000_login_start, so the agent must infer the sequence.

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?

The description implies this is the step after a device code is issued and notes the 60-second wait per call, but it never states when to use this versus auth_status, whether to retry after a timeout, or what prerequisites exist.

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