Skip to main content
Glama
Sign In

Keryx

by io.github.tang-vu
OverviewDiscussionsAdmin

Export your question record

run_owner_export
Read-onlyIdempotent

Owner-private current-store read using the verified key's explicit history:read scope. No wallet selector or signing. Visibility, defaults and erasure require the interactive web session. Storage admission is required.

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": {
      "id": "<id>",
      "requestId": "<requestId>"
    },
    "name": "run_owner_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesExisting current-store run ID owned by the authenticated key's wallet.
requestIdYesCaller-generated UUID identifying this manual export request in its audit record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"Existing current-store run ID owned by the authenticated key's wallet."
    • addedInput schema / properties / requestId / description
      Added value: +"Caller-generated UUID identifying this manual export request in its audit record."
  2. Added

TDQS

B3.2/5.0
Behavior4/5

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

Beyond annotations, it discloses auth scope, absence of wallet selector/signing, and web-session-only operations, which is useful context for a read-only export. It still leaves 'storage admission' unexplained and does not mention the audit record implied by requestId, but overall adds real context to the readOnly/idempotent annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences are reasonably front-loaded, but the prose is jargon-heavy ('current-store,' 'storage admission') and the final sentence is a dangling prerequisite. It is concise without being fully clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The auth and scope constraints are covered, but with no output schema the description should explain what an export returns or how the record is delivered. It also leaves the storage-admission prerequisite and audit-record behavior opaque.

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 coverage is 100%, so id and requestId are fully documented in the schema; the description adds no parameter-level meaning. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The title says 'Export your question record' and the description calls it an 'Owner-private current-store read,' so the broad purpose is inferable, but the description never plainly states that it exports a run/question record. 'Current-store' is undefined and no sibling tool is named to sharpen the distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives prerequisites (verified key with history:read, storage admission) and exclusions (visibility/defaults/erasure need the interactive web session), but it never routes the agent to a specific sibling such as history_export or history_owned_read. The when-to-use guidance is implied rather than explicit.

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

All Keryx 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