Webanto

Get MCP support options

webanto_get_mcp_support

Read-onlyIdempotent

Read Webanto's MCP support routes. Public protocol issues use Koskamo's directory tools; private customer and organization requests stay in Webanto's authenticated support portal. This reports no issue or outcome and sends no caller data.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`server`	Yes
`privacy`	Yes
`service`	Yes
`visibility`	Yes
`schema_version`	Yes
`private_help_path`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: 'This reports no issue or outcome and sends no caller data,' clarifying it is purely informational and transmits nothing. That is a meaningful addition beyond the structured fields.

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 short sentences, front-loaded with the core action, then the routing distinction, then the no-side-effect guarantee. Every sentence carries distinct information and nothing is repeated from the title or annotations.

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?

With zero parameters and an output schema present, the description need not explain return values, and it doesn't. It covers purpose, routing, and side-effect behavior. The only minor gap is that 'support routes' could be slightly more concrete about what the caller receives, but the output schema fills that role.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly does not waste words on inputs.

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 opens with a specific verb and resource: 'Read Webanto's MCP support routes.' It distinguishes itself from sibling tools by naming the two routing destinations (Koskamo's directory tools vs. Webanto's authenticated support portal). The only weakness is that 'support routes' is somewhat abstract — an agent must infer this returns routing/contact information rather than tickets or issues.

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 explicit routing conditions: public protocol issues go to Koskamo's directory tools, private customer/organization requests go to Webanto's authenticated support portal. This tells the agent which path applies to which situation. It stops short of saying 'call this tool when you need to determine which path applies,' leaving that inference to the agent.

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

All Webanto tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?