Skip to main content
Glama

sdk-get_ast_schema

Retrieve JSON Schema definitions for Exeris build-time DomainMetadata AST records. Request the top-level schema or a specific definition such as DomainMetadata, FieldMetadata, or ActionMetadata.

Instructions

Get JSON Schema for the Exeris build-time DomainMetadata AST and sibling records. If 'definition' is omitted, returns the top-level schema envelope, reader requirements (such as Jackson 3 constraints), and definition list. If 'definition' is specified (e.g. 'DomainMetadata', 'FieldMetadata', 'ActionMetadata'), returns the schema definition for that specific record.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sdk-get_ast_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
definitionNoOptional AST definition name (e.g. 'DomainMetadata', 'FieldMetadata', 'ActionMetadata').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does disclose the branching return behavior: envelope plus reader requirements and definition list versus a single record's schema. It doesn't state access requirements, whether output is static/cached, or error behavior for an unknown definition name, which are the remaining gaps for a zero-annotation tool.

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?

Two sentences, front-loaded with the resource, then the two behavioral branches in the order an agent needs them. The parenthetical 'such as Jackson 3 constraints' earns its place by warning about reader requirements; there is 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 single optional-parameter lookup with no output schema and no annotations, the description covers both call modes and what each returns, which is the core need. It could go slightly further on unknown-definition handling and stability of the schema, but nothing essential for correct invocation is missing.

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

Parameters4/5

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

Schema coverage is already 100%, so the schema documents the parameter's type and examples. The description nevertheless adds real meaning beyond it by explaining the semantic effect of omitting the parameter versus supplying one, which the schema does not express.

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?

The description opens with a specific verb and resource: 'Get JSON Schema for the Exeris build-time DomainMetadata AST and sibling records.' An agent immediately knows this is a schema-lookup tool, not a metadata-value or docs tool. It does not, however, distinguish itself from near-neighbours such as build-get_domain_metadata, leaving that separation implicit.

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?

The two-mode structure ('If definition is omitted...' / 'If definition is specified...') effectively tells the agent when to call it with and without the parameter, which is the main usage decision here. There are no explicit exclusions or named alternatives for adjacent tools, so it stops short of full routing guidance.

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