Locus

Read call result

get_call_result

Read-onlyIdempotent

Read an earlier call's stored result by receipt ID in chunks (offset or page, max_characters); wait_seconds waits for a still-running call. Use when execute truncated the result. Free.

Input Schema

Name	Required	Description
`page`	No	Prior next_page.
`offset`	No	Character offset; default 0.
`api_call_id`	Yes	Receipt ID.
`wait_seconds`	No	Async wait.
`max_characters`	No	Default 8000.

Output Schema

Name	Required	Description	Default
`chunk`	No
`api_call_id`	No
`total_characters`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 7, 2026

changedInput schema / properties / api_call_id / description

Previous value: -"execute call or capability receipt ID."New value: +"Receipt ID."

changedInput schema / properties / max_characters / description

Previous value: -"Characters: default 8000, max 20000."New value: +"Default 8000."

addedInput schema / properties / page

Added value: +{
+  "description": "Prior next_page.",
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / wait_seconds

Added value: +{
+  "description": "Async wait.",
+  "maximum": 45,
+  "minimum": 0,
+  "type": "integer"
+}

removedOutput schema / additionalProperties
```
Removed value: -true
```
removedOutput schema / properties / api_call_id / description
```
Removed value: -"Receipt ID."
```
removedOutput schema / properties / chunk / description
```
Removed value: -"Result text slice."
```
removedOutput schema / properties / total_characters / description
```
Removed value: -"Full stored result length."
```

Changed1 schema field changedSep 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "api_call_id": {
+      "description": "Receipt ID.",
+      "type": "string"
+    },
+    "chunk": {
+      "description": "Result text slice.",
+      "type": "string"
+    },
+    "total_characters": {
+      "description": "Full stored result length.",
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

First observedSep 15, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context beyond those hints by explaining chunked reading, offset/page handling, async waiting, and that the operation is free.

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 single sentence is densely packed but front-loaded with the core action and receipt ID, then adds truncation, chunking, and wait behavior. Every clause carries operational value.

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?

The tool has an output schema, rich annotations, and fully documented parameters. The description supplies the missing usage context: when to call it, how chunking works, and what wait_seconds does.

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 100%, so the baseline is 3. The description still adds meaning by clarifying that results are read in chunks using offset or page and max_characters, and that wait_seconds controls waiting for a still-running call.

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 states a specific verb and resource: read a stored call result by receipt ID. It also distinguishes the tool from execute by saying to use it when execute truncated the result, so an agent can identify its role without opening the schema.

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?

It gives a clear trigger condition: use when execute truncated the result, and explains that wait_seconds is for a still-running call. It does not state explicit exclusions or name alternative tools, but the operative context is unambiguous.

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

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