roki_list_operationsList every operation the API actually exposes, plus the operations that are documented as NOT existing. Call this before writing any integration code so you never invent an endpoint.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true; the description adds the valuable detail that it also lists operations documented as NOT existing, which is a beyond-annotations behavioral trait. This gives the agent a clear expectation of the response scope.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the action, no filler. The instruction 'Call this before...' earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, no-output-schema listing tool, the description fully covers purpose, usage, and the unusual inclusion of non-existing operations. Complete as is.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has zero parameters, so baseline is 4. No parameter info is needed; schema coverage is trivially 100%.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description states 'List every operation the API actually exposes, plus the operations that are documented as NOT existing' – a specific verb+resource with clear scope. It also distinguishes from sibling get_operation by framing it as the pre-coding discovery step.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly instructs 'Call this before writing any integration code so you never invent an endpoint,' providing a clear when-to-use context. Doesn't name explicit alternatives or when-not-to-use, but the trigger is specific.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose, from searching docs to validating requests to verifying webhook signatures. Even similarly named tools like roki_get_integration_example and roki_scaffold_integration are differentiated by 'complete runnable' vs 'skeleton'.
Tools mostly follow a roki_verb_noun pattern (get, list, search, validate, verify), but a few deviate with noun-only names like roki_status and roki_sandbox_info. The prefix and clear verbs make the pattern predictable overall.
18 tools is on the heavy side, but each serves a distinct role in the integration workflow covered by this server. The count is justified given the breadth of documentation, validation, sandbox, and example generation features.
The tool surface covers the full lifecycle of an integration: discovery (search_docs, list_operations), learning (guides, examples, schemas), validation (validate_request), sandbox testing (sandbox_try), verification (verify_webhook_signature), and post-integration auditing. No obvious gaps for the server's stated purpose.