antideploy-mcp

Official

by antideploy

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

Read the API's own manual

api_info

Read-only

Retrieve the platform's current API self-description—endpoints, limits, and behavior—to verify server responses when documentation disagrees.

Instructions

The platform's self-description: endpoints, limits and current behaviour. Worth reading whenever something here disagrees with what the server does.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

readOnlyHint=true and openWorldHint=false already establish the safety profile, so the description only needs to add context. It does: the payload includes limits and 'current behaviour', and the caveat about disagreement implies the manual may lag the live server — useful for an agent deciding whether to trust it. It says nothing about response size or structure, which keeps it below 5.

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 short sentences, no filler, with the content scope front-loaded and the usage hint second. Every clause carries information an agent can act on.

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

Completeness4/5

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

For a no-argument documentation fetch with no output schema, the description tells the agent what topics the response covers and when it is worth consulting. The only real gap is that the return shape and size are unstated, which an agent may want to know before pulling a large manual.

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?

Zero parameters, so there is no parameter semantics to explain; baseline is 4. The schema is empty and fully described, and the description correctly implies a single no-argument call.

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 specifies the resource precisely: the platform's own self-description covering endpoints, limits, and current behaviour. That content set distinguishes it from operational siblings like health, metrics, and logs, which report live state rather than documentation. It lacks an explicit verb ('returns'/'fetches'), but the noun phrase is unambiguous.

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?

It gives a concrete trigger: read it when something here disagrees with what the server actually does. That is a specific, actionable usage condition rather than vague encouragement. It does not name alternatives (health, logs) or state when not to bother, so it stops short of a full 5.

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