Skip to main content
Glama

Read a project's inputs and outputs

metamodel_get_schema
Read-only

Get the input/output schema for a published MetaModel project. Returns model names, input parameters (with types, defaults, validation), and output fields. Models marked "presentation": true are display scaffolding (3D scenes etc.) — skip them for engineering analysis. Use a token from metamodel_list_projects.

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_get_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesThe publish token of the project (from metamodel_list_projects)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds genuinely useful behavioral context beyond that: the shape of the returned payload and the meaning of the "presentation": true flag, which would otherwise cause an agent to misread display scaffolding as engineering models. Error behavior for a bad token is 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, each doing distinct work: purpose, return contents, and an interpretation warning. Front-loaded with the core action and no filler.

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?

For a one-parameter read-only tool with no output schema, the description correctly compensates by describing return contents and the presentation-model caveat. Only the failure mode (invalid or expired token) is left unaddressed, which is a minor gap.

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?

There is a single parameter at 100% schema description coverage, and the schema already states 'The publish token of the project (from metamodel_list_projects)'. The description's token guidance therefore repeats structured data rather than adding format, sourcing, or failure semantics — baseline 3 is appropriate.

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 first sentence states a specific verb and resource — 'Get the input/output schema for a published MetaModel project' — and the follow-up enumerates exactly what is contained (model names, input parameters, output fields). This is clearly distinguishable from the list and compute siblings without opening any schema.

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 gives a concrete prerequisite ('Use a token from metamodel_list_projects') and an explicit filtering rule for interpreting results (skip models marked "presentation": true for engineering analysis). It stops short of naming when to prefer metamodel_compute or what to do if the token is invalid, so no full when/when-not/alternatives triad.

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.