MCP Server

api-client

Process messages through a unified API that connects to multiple AI providers, enabling interaction with services like Anthropic Claude and OpenAI via Cloudflare Workers.

Instructions

ApiClient tool description

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": "api-client"
  }
}

Input Schema

Name	Required	Description	Default
`message`	No	Message to process

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 15, 2025

TDQS

D1.4/5.0

Behavior1/5

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

With no annotations, the description bears full responsibility for disclosing behavioral traits. It fails to mention any side effects, authorization needs, rate limits, or return characteristics, offering only the generic name.

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

Conciseness2/5

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

The description is short but wastes its single sentence on a tautology. It is under-specified rather than concise, as it omits essential information that a longer description would provide.

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

Completeness1/5

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

Given the tool's generic name and the presence of siblings, the description is wholly incomplete. It does not mention the API being communicated with, the expected output, or any special behavior, rendering it insufficient for an agent to use correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so the parameter 'message' is already documented in the input schema. The description adds no additional meaning or constraints beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'ApiClient tool description' is a tautology that merely restates the tool name without specifying any verb, resource, or action. It does not distinguish this tool from siblings like 'data-processor' or 'file-handler'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool vs. alternatives. The description lacks any context, prerequisites, or examples, leaving the agent without any decision-making support.

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

Deploy Server