mcp-server-polymarket

Overview Schema Source Related Servers Discussions Admin

Show what this server can do

auth_status

Read-onlyIdempotent

Reports the configured signer and wallet, detected credentials, open write gates, and hidden tools with the settings needed to enable them; secrets are never displayed.

Instructions

Report the configured signer and wallet, which credentials were found, which write gates are open, and which tools are hidden and what would enable them. Secrets are never shown. Tools appear only after the server restarts with the new configuration.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`notes`	No
`hidden`	Yes
`toolsets`	Yes
`gates_open`	Yes
`credentials`	Yes
`signer_role`	Yes
`signer_address`	No
`wallet_address`	No
`signing_extra_installed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses two non-obvious behaviors an agent could not otherwise know: secrets are deliberately omitted from the output, and tool visibility only updates after a server restart with the new configuration. Those details directly shape how an agent should interpret and act on the result.

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?

Three sentences, front-loaded with the report contents, followed by the secrets guarantee and the restart caveat. Every sentence carries distinct information and none restates structured fields.

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 zero-argument, read-only diagnostic with an output schema and full annotations, the description covers what an agent needs to know to call and interpret it. Only minor gaps remain, such as whether the call itself requires authentication or how failures are reported.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. No misleading parameter hints are present.

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 names a specific verb ('Report') and enumerates exactly what is reported: configured signer and wallet, found credentials, open write gates, and hidden tools with their enablement conditions. That scope is unmistakably diagnostic/auth-configuration work, clearly separable from the market-data and profile siblings.

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?

Usage is only implied: an agent can infer this is the tool to call when it needs to know why a write is blocked or why a tool is missing. There is no explicit 'use this when...' clause, no statement of when not to use it, and no named alternative such as get_service_status for general server health.

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

Deploy Server