Skip to main content
Glama

get_result

Retrieve results from a completed conjoint fit, or request one section (derived, params, fit, baselines, meta) to inspect estimates and diagnostics without loading the full output.

Instructions

The results JSON of a finished fit. Large; pass section to get one part: derived (part-worths, importances, WTP), params (mean tastes, taste spread, error shares), fit (log-likelihood, holdout hit rate, warnings), baselines (comparison models), meta (settings, design). Every estimate is {est, se, lo, hi} with a 95% range.

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": {
      "fit_id": "<fit_id>"
    },
    "name": "get_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
fit_idYes
sectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it warns the output is 'Large' and offers the section parameter as the mitigation, and it discloses the shape of every estimate ({est, se, lo, hi} with a 95% range). Auth requirements, error behavior, and whether results persist are not covered.

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?

Front-loads the key fact ('results JSON of a finished fit') and then the size warning plus the workaround. Dense and nearly waste-free, though the parenthetical section enumeration makes it a long run-on sentence.

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?

No output schema exists, so the description must explain return values, and it does so at both the section level and the individual-estimate level. What remains missing is minor: fit_id semantics and behavior when the fit is not finished.

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 0%, so the description must compensate, and it does for 'section': it names all five valid values and the contents of each (part-worths, WTP, log-likelihood, holdout hit rate, warnings, etc.). 'fit_id' is left undocumented, which is the only real gap.

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?

States a specific resource: the results JSON of a finished fit, and enumerates the five sections it contains. An agent can tell this apart from fit_status or list_projects by the returned payload, though the description never explicitly contrasts them.

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 'of a finished fit' implies a precondition (the fit must be complete), which hints at needing fit_status or wait_for_fit first, but this is never stated. There is no explicit guidance on when to call with a section vs. without, nor any named alternative.

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