OpenArx

methodist_get

Fetch a scientific record by id (claim/relation/activity/metric/bundle). Process records (run/intent/decision/journal) are never exposed — the exposure boundary (§12.4/§12.5). Process-referencing fields are stripped. ★ key_origin rides beside the record: for each field, derived (the platform established it — verification, link_strength, is_superseded, id), authored_gated (the author declared it and the platform can check it — an excerpt against its document) or authored_open (declared, checkable by no one but you — the text, the status, the author's own grounding estimate). A field the map does not name is authored_open.

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>"
    },
    "name": "methodist_get"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`run_id`	No	Optional. The active methodist run_id (as returned by the methodist diagnose / get_current_dose door). Pass it whenever you call this tool while working inside a run, so the call is attributed to that run for the §8 usage crosscheck — attribution is run-anchored, so it stays correct even if your access token refreshes mid-run. Must be YOUR run: a run_id owned by a different principal, or a non-existent run_id, is rejected.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations provided, the description bears the full disclosure burden. It does substantial work by revealing that process-referencing fields are stripped secret, that the exposure boundary is enforced, and that each field carries a key_origin classification (derived, authored_gated, authored_open) with a default rule for unmapped fields. It does not cover error/not-found behavior or authentication prerequisites, but the disclosed behavioral traits are rich.

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

Conciseness4/5

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

The core verb-resource clause is front-loaded, and the ensuing provenance details are dense but purposeful given that there is no output schema to carry that context. The § references and key_origin taxonomy are terse rather than padded. It is longer than a minimal one-liner, but the complexity of the tool justifies the added explanation.

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?

For an id-lookup tool with no annotations and no output schema, the description covers the critical facts: accepted record kinds, the process-record exclusion boundary, field stripping, and the key_origin provenance model. The only notable gaps are explicit routing guidance relative to sibling find/search tools and a precise response envelope. Overall it is close to complete for this tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: id is simply a string while run_id has a detailed description. The tool description compensates by clarifying that id refers to scientific record types and that process record ids are invalid because they are never exposed. run_id's semantics are already fully provided in the schema, so the combined effect is strong parameter meaning.

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 opening sentence states a precise verb and resource: 'Fetch a scientific record by id (claim/relation/activity/metric/bundle).' It enumerates the accepted record types and explicitly distinguishes scientific records from process records, which prevents confusion with the many sibling methodist tools. This is a very specific, non-tautological purpose statement.

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 gives clear context: call this tool when you have an id and need a scientific record, and it explicitly warns not to expect process records because they are 'never exposed.' It stops short of naming a sibling alternative for when the id is unknown, so it earns 4 rather than 5.

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

All OpenArx 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.