Skip to main content
Glama
mefcs-mcp

mefcs-mcp

by cayocan

Save TONE3000 keys

tone3000_set_credentials

Saves a TONE3000 client ID or secret API key on this computer and starts login, letting the MCP server access TONE3000 tones and models.

Instructions

Save the TONE3000 publishable key (client id, preferred) and/or secret key (t3k_cs_...) on this computer, then start the login. Keys come from https://www.tone3000.com/settings.

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

Input Schema

NameRequiredDescriptionDefault
apiKeyNo
clientIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that secrets are persisted on the local computer and that the login is then started, but omits overwrite behavior, what happens when one or both keys are absent, where the secret is stored, and what the login step actually triggers.

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?

Two front-loaded sentences with no filler; the key-source URL is a useful addition rather than padding. The trailing 'then start the login' clause is slightly ambiguous but still earns its place.

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?

For a small two-parameter tool with no annotations or output schema, the essentials (what is saved, in what format, from where, and that login follows) are present, but the ambiguity around its relationship to the standalone login tools leaves an agent unsure of the correct call sequence.

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?

Schema coverage is 0%, so the description must compensate. It maps the two bare parameters to real concepts (clientId = publishable key, apiKey = secret key with the t3k_cs_ prefix), signals 'and/or' semantics, expresses a preference for the client id, and points to where the keys come from.

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?

Names a specific verb and resource (save TONE3000 publishable/secret keys on this machine) and reveals a follow-on side effect (starting the login). It is distinguishable from siblings like tone3000_auth_status, though the overlap with tone3000_login_start is not resolved.

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 the prerequisite context (supply keys before logging in) and marks the client id as 'preferred', but it never states when to use this instead of tone3000_login_start, nor whether calling this alone is sufficient to complete authentication.

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