Webanto

List organization support tickets

webanto_list_support_tickets

Read-onlyIdempotent

Read a bounded live page of client-visible tickets in exactly the key organization. Native account-wide visibility is intersected with that organization; personal and other-workspace tickets are excluded. Billing-category tickets additionally require billing:read scope and live billing permission, including for the opener. No replies, status changes or inference credits.

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

Input Schema

Name	Required	Description	Default
`cursor`	No	Opaque next_cursor from the preceding live page with the same filters; omit for the first page.
`page_size`	No	Maximum records in this page; at most 20.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Goes well beyond the supplied readOnly/idempotent annotations by disclosing the permission model (billing:read + live billing permission, including for the opener), the visibility intersection rule, and that no mutations or credit spend occur. The only gaps are the cryptic 'live'/'inference credits' wording, which leaves caching and cost behavior implicit.

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 tight sentences, scope front-loaded before permission caveats, with no filler. The trailing negation clause ('no replies, status changes or inference credits') is compact and does real work.

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?

An output schema exists so return values need no explanation, both parameters are schema-documented, and the description covers the access-control nuances that an agent would otherwise get wrong. Nothing material is missing for correct invocation.

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% and both cursor and page_size are fully documented in-schema, so the baseline is 3. The phrase 'bounded live page' hints at pagination, but the description adds no cursor format, page-size cap, or filtering semantics beyond what the schema already states.

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?

States a specific verb and resource (read a bounded live page of client-visible tickets) plus the exact scoping rule (only the key organization). An agent can immediately tell this is a filtered org-level listing rather than a single-record fetch like the sibling webanto_get_support_ticket.

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?

Gives clear inclusion/exclusion rules: personal and other-workspace tickets are excluded, and billing-category tickets need billing:read scope plus live billing permission even for the opener. It stops short of explicitly routing the agent to webanto_get_support_ticket for full record detail, so it is clear context rather than a full when/when-not/alternatives statement.

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?