Skip to main content
Glama

Feature Schema

feature_schema
Read-only

Retrieve a feature template's declared reference geometry and scalar parameters—including types, units, defaults, ranges, and required inputs—so you can validate or configure a design before use.

Instructions

Return one feature template's declared REF+INPUT SCHEMA — its reference geometry (name/kind) and its scalar parameters (type/unit/default/range). Returns {schema, template, doc, refs:[{name, kind, required, doc?}], inputs:[{name, type, unit?, default?, min?, max?, required, choices?, doc?}], emits}. An unknown name fails loudly.

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": {
      "template": "<template>"
    },
    "name": "feature_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateYes
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds real context beyond that: it spells out the return shape field-by-field and discloses the failure mode ('An unknown name fails loudly'), which is important for an agent that must not guess template names. It stops short of describing errors more precisely (error type, whether a list of valid names is returned).

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-loaded with the core purpose, followed by the return shape and one behavioral caveat; no filler sentences. The inline type notation for the return object is dense but justified given there is no output schema.

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 compensates by enumerating the returned keys and their subfields, which is exactly what an agent needs before calling. The remaining gap is provenance of the `template` argument and any hint that results are static/declarative rather than tied to document state.

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 coverage is 50%: `workspace` is documented in the schema while `template` is bare. The description implies `template` is a name identifying one template and that an unknown name fails, which adds some meaning, but it does not say the expected format or source of that name (e.g., an id returned by feature_list). Baseline 3 for a schema that carries half the load.

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?

States a specific verb (return) and resource (one feature template's REF+INPUT schema) and immediately enumerates what that schema contains (reference geometry name/kind, scalar parameters type/unit/default/range). This clearly separates it from siblings like feature_list (enumerate templates), feature_validate (check a definition), and feature_instantiate (create a feature).

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 usage is only implied: an agent can infer it is a pre-instantiation introspection call, but the description never says when to prefer it over feature_list, feature_validate, or catalog_search, nor does it state any prerequisite such as where the template name must come from. Adequate but with a clear routing gap.

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

Deploy Server

Other Tools