Skip to main content
Glama

Get a running quant answer

get_quant_result
Read-onlyIdempotent

Returns a Sortefi quant answer that was still being worked out when ask_quant replied, using the reference ask_quant gave. Never charges again.

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": {
      "ref": "<ref>"
    },
    "name": "get_quant_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesThe reference ask_quant returned, e.g. "aq_3f9c1a2b7d4e".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new information beyond them: 'Never charges again,' which tells the agent there is no repeated billing cost for polling. It doesn't say whether the call blocks, returns a pending status, or errors when the job is incomplete, which is the main behavioral unknown left.

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?

A single sentence with no filler. The retrieval action and its dependency on ask_quant's output are front-loaded, and the billing reassurance follows compactly.

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?

For a one-parameter, fully documented, annotated polling tool this is close to sufficient, but there is no output schema, so the description should say what comes back when the answer is still unfinished (partial result, status field, or error). That gap matters for a tool whose whole purpose is checking an in-progress job.

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% and the schema already provides an example ref format, so the baseline is 3. The description adds provenance the schema lacks: the ref is the one ask_quant returned, which tells the agent where to source the value rather than inventing one.

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 gives a specific verb ('Returns') and resource ('a Sortefi quant answer'), and names the sibling ask_quant as the tool that produced the reference. It clearly distinguishes this polling tool from the ask_quant call that started the job.

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 clearly states when to use it: when ask_quant replied while the answer was still being worked out, using the ref ask_quant gave. It doesn't cover when to stop polling, how often to retry, or what to do if the result is still pending, so it's clear context without exclusions.

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