Skip to main content
Glama
Sign In

ROKI Connect

by la.roki
OverviewDiscussionsAdmin

Choose the right ROKI integration approach

roki_choose_integration_mode
Read-onlyIdempotent

Decide how to integrate ROKI Connect for a given project (web checkout, embedded card fields, mobile app, invoices or recurring billing) and get the constraints that apply before writing code. The modes and the endpoints behind them are read from the corpus, so this answer cannot describe a mode the API no longer has - or miss one it gained.

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": {
      "context": "<context>"
    },
    "name": "roki_choose_integration_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesWhat the project is: e.g. "Laravel e-commerce checkout", "iOS app", "card fields on my own page", "invoices from an ERP", "monthly subscriptions".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / context / description
      Previous value: -"What the project is: e.g. \"Laravel e-commerce checkout\", \"iOS app\", \"invoices from an ERP\", \"subscriptions\"."New value: +"What the project is: e.g. \"Laravel e-commerce checkout\", \"iOS app\", \"card fields on my own page\", \"invoices from an ERP\", \"monthly subscriptions\"."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark the tool as readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds valuable context by explaining that modes and endpoints are read from the corpus, ensuring up-to-date information. This goes beyond annotations and clarifies the tool's dynamic nature, but it does not elaborate on output format or potential side effects (which are unlikely given annotations).

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 two sentences long, with the purpose in the first sentence and an important behavioral note in the second. There is no fluff or redundant repetition. Every sentence earns its place, and the most critical information (purpose) is front-loaded.

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?

Given the simplicity of the tool (one parameter, no output schema), the description covers essential aspects: what it does, when to use it, and how it stays current. It does not explicitly state the return format, but the phrase 'get the constraints that apply' implies the output content. An explicit mention of return structure would improve completeness, but this is a minor gap, not a fatal flaw.

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 input schema has 100% coverage for the single 'context' parameter, with a clear description and examples. The tool description repeats some examples (web checkout, mobile app, etc.) but adds no new information beyond the schema. This aligns with the baseline score of 3 for high schema coverage; the description does not compensate for any gaps because there are none.

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's purpose: 'Decide how to integrate ROKI Connect for a given project' and lists specific integration modes (web checkout, embedded card fields, mobile app, etc.). It distinguishes itself from sibling tools like roki_search_docs or roki_get_integration_example by focusing on mode selection and constraints, not documentation lookup or code examples.

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 specifies the intended use case: before writing code, for a given project. It enumerates project types, giving clear context for when to invoke the tool. However, it does not explicitly state when not to use it or name alternative tools, so it lacks explicit exclusions but is still clear enough for a competent agent.

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

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