Skip to main content
Glama

Get public scenario result

get_public_scenario_result
Read-onlyIdempotent

Read an already published public scenario result, preserving provenance and warnings. Missing publication is explicitly unavailable, never a new simulation or a zero result. No parameter overrides or server compute.

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": {
      "model_id": "<model_id>",
      "scenario_id": "<scenario_id>"
    },
    "name": "get_public_scenario_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_idYes
scenario_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 non-obvious behavior: missing publication surfaces as an explicit 'unavailable' state rather than a zero result or a fresh simulation, and provenance/warnings are preserved in the response. That failure-mode disclosure is the kind of context annotations cannot carry.

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?

Three short sentences, front-loaded with the action and resource, with no filler. The negative phrasing ('never a new simulation or a zero result', 'No parameter overrides or server compute') is dense but each clause carries distinct information.

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?

An output schema exists, so return values needn't be spelled out, and the safety profile is fully covered by annotations; the description correctly focuses on the missing-publication edge case. The remaining gap is the identity of the two required parameters, which neither schema nor description explains for a tool whose correctness depends on addressing the right published result.

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 explain model_id and scenario_id and it does not — neither parameter is mentioned. 'No parameter overrides' describes what the tool rejects, not what the two required identifiers mean or how they jointly address a published result.

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 verb ('Read') and resource ('already published public scenario result'), which separates it from get_public_model and list_public_models by resource type. It does not name a sibling for direct routing, but the resource scope is unambiguous.

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?

Usage context is implied by 'already published' — the caller must have a publication in hand — and the exclusion 'No parameter overrides or server compute' rules out a compute-style call. However, it never explicitly says when to prefer this over get_public_model or list_public_models, leaving routing to inference.

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