Skip to main content
Glama

get_simulation_deliverables

Fetch KPIs and download URLs (PDF report, A3 drawings, .dxf, .xlsx, bundle.zip).

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": {
      "job_id": "<job_id>"
    },
    "name": "get_simulation_deliverables"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the returned payload types (KPIs, PDF, A3 drawings, .dxf, .xlsx, bundle.zip), but says nothing about required job state, whether artifacts may be missing, or how errors are surfaced for an incomplete job.

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?

A single front-loaded sentence with no filler, and the parenthetical enumeration of formats is efficient. It is arguably too terse for the tool's role, but nothing in it is wasted.

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 retrieval tool with no output schema, the description does convey what comes back and in which formats. It falls short on the missing pieces an agent needs: the meaning/source of job_id and the readiness requirement before deliverables exist.

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?

There is one required parameter (job_id) with 0% schema description coverage, and the description never mentions it or explains its expected format/source. The agent must guess that job_id is the identifier returned by a prior simulation run.

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?

Uses a specific verb ("Fetch") plus a concrete resource ("KPIs and download URLs") and enumerates the deliverable formats, so the agent knows it retrieves results rather than running anything. It is naturally distinguishable from the run_* siblings by the retrieval verb, though it never explicitly contrasts itself with 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 verb "Fetch" and the deliverable framing imply this is the post-run retrieval step, which lets an agent infer it follows a simulation. However, there is no explicit statement of when to call it (e.g., only after a job completes), no prerequisites, and no named alternative.

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