Skip to main content
Glama

Compute a project

metamodel_compute
Read-only

Run a computation on a MetaModel project. Send input values and get computed outputs from all models. Inputs are auto-routed to the correct model by property name. Models marked "presentation": true in results are display scaffolding, not engineering outputs. Use metamodel_get_schema first to discover available inputs and outputs.

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": {
      "token": "<token>"
    },
    "name": "metamodel_compute"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoTarget a specific model by name. When omitted, returns outputs from ALL models (recommended).
tokenYesThe publish token of the project
inputsNoInput values as key-value pairs (e.g., {"width": 12}). Auto-routed to the correct model. Omitted inputs use defaults.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the operation read-only, closed-world, and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: auto-routing of inputs by property name, defaulting of omitted inputs, and the caveat that "presentation": true results are scaffolding rather than engineering outputs. It still says nothing about computation cost, latency, failure modes for invalid property names, or the shape of the returned results.

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?

Four short sentences, front-loaded with the action and followed by the operational caveats in roughly the order an agent needs them. The opening sentence and "get computed outputs from all models" overlap slightly, but nothing is padded or buried.

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?

With no output schema, the description carries the burden of explaining returns, and it does so at a high level: outputs from all models plus the "presentation" flag caveat. Combined with a fully documented input schema and read-only annotations, an agent has enough to call it correctly. Only the precise response structure and error behavior remain unstated.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already explains `model`, `token`, and `inputs` including the auto-routing and default behavior. The description largely restates that same meaning rather than adding syntax, naming constraints, or examples beyond what the schema gives. Baseline 3 is appropriate.

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?

Specific verb+resource ("Run a computation on a MetaModel project") with a clear statement of what flows in and out (input values -> computed outputs from all models). It also distinguishes itself from metamodel_get_schema by naming it as a prerequisite rather than a substitute. It stops short of a full sibling contrast (e.g., versus metamodel_list_projects), but an agent can still tell these apart.

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?

"Use metamodel_get_schema first to discover available inputs and outputs" gives an explicit ordering prerequisite, which is the main usage hazard for a compute tool with free-form inputs. The schema's note that omitting `model` returns all models reinforces the recommended path. No explicit when-not-to-use case is given, so it falls short of a 5.

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.