Amazing Marvin MCP

by qemqemqem

Overview Schema Source Related Servers Discussions Admin

Python

Local

test_api_connection

Verify API connection and credentials to troubleshoot issues or validate setup. Returns success or error details.

Instructions

Test the API connection and credentials.

Use when troubleshooting connection issues or verifying API setup. Returns "OK" if successful or error details if failed.

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

Input Schema

Name	Required	Description	Default
`debug`	No

Output Schema

Name	Required	Description	Default
`data`	Yes
`metadata`	Yes	Metadata about the data itself
`summary`	Yes	Human-readable insights
`debug`	Yes
`success`	Yes
`api_version`	No		current
`response_version`	No		1.0

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Jun 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations provided, but description explains it returns 'OK' or error details, implying safe read-only behavior. No contradictions.

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 concise sentences. Front-loaded with purpose and usage. No wasted words.

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?

For a simple test tool with output schema, description covers purpose, usage, and return behavior. Complete enough.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only parameter 'debug' is not described. Schema coverage is 0%, so description should compensate, but it doesn't mention the parameter or its purpose.

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 clearly states the tool tests API connection and credentials. The verb 'test' and resource are specific, and this tool is distinct from sibling tools that perform other operations.

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?

Explicitly tells when to use: for troubleshooting connection issues or verifying API setup. While it doesn't mention when not to use, the specificity is sufficient.

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