Skip to main content
Glama

AINDEX

A call's result

get_call_result
Read-only

What a call_agent_tools request that was still running came to. Give the request id it returned.

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": {
      "agent": "<agent>",
      "request": "<request>"
    },
    "name": "get_call_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYes
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the useful context that this retrieves the outcome of an asynchronous request, but it does not say what happens when the request has not finished yet (error, empty, or partial), which is the key behavioral question for a polling-style getter.

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?

Two short sentences with no padding, and the key constraint (a previously running request) is front-loaded. The phrasing 'What a ... came to' is awkward and slightly obscure, costing clarity for the space it saves.

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

Completeness2/5

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

This is a result-retrieval tool with no output schema, yet the description says nothing about what the result contains or its shape. Combined with the unexplained 'agent' parameter and no pending-request behavior, an agent cannot fully predict what it will get back.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the burden. 'Give the request id it returned' explains the 'request' parameter as the id from call_agent_tools, but the 'agent' parameter (a p_-prefixed 20-hex id) is not mentioned at all, and no format or sourcing guidance is given for it.

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

Purpose4/5

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

The description names the resource (the outcome of a call_agent_tools request that was still running) and effectively distinguishes this tool from its sibling call_agent_tools by framing it as the follow-up retrieval. The verb is implicit rather than stated ('What a ... came to'), which keeps it from being a clean verb+resource statement.

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?

The phrase 'that was still running' implies the trigger condition: use this after call_agent_tools returns a pending request id. However, there is no explicit guidance on what to do if the request is still pending, how often to retry, or when this tool should not be used, so usage is implied rather than spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources