ROKI Connect

Get a ROKI Connect API operation in full

roki_get_operation

Read-onlyIdempotent

Full detail for one operation: method, path, headers, request schema field table, responses, and worked examples.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operation": "<operation>"
    },
    "name": "roki_get_operation"
  }
}

Input Schema

Name	Required	Description	Default
`operation`	Yes	operationId (e.g. "createPayment"), or "METHOD /path" (e.g. "POST /payments").

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 17, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, establishing a safe, read-only profile. The description adds valuable context by disclosing the exact contents of the returned detail: method, path, headers, request schema field table, responses, and worked examples.

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?

The description is a single sentence that front-loads the purpose and uses a colon to introduce the list of included components. Every word earns its place, with no redundancy or filler.

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?

This is a simple read-only retrieval tool with one well-defined parameter, no output schema, and rich annotations. The description fully covers what the tool returns and the schema fully covers the input, making the tool sufficiently documented for a capable agent.

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?

The single parameter 'operation' is fully described in the schema with concrete examples (operationId or METHOD /path). The tool description itself does not add additional parameter semantics, and since schema_description_coverage is 100%, the baseline score of 3 is appropriate.

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 clearly states the tool retrieves full details of a single API operation, enumerating method, path, headers, request schema field table, responses, and worked examples. It distinguishes itself from sibling tools like roki_list_operations (which lists operations) by focusing on one operation in full.

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?

The description implies the tool is for when you need comprehensive details of a single operation, as opposed to listing operations. While it does not explicitly name alternatives, the focus on 'one operation' provides clear context for when to use it, and no exclusions are stated.

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

All ROKI Connect 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?