Skip to main content
Glama

get_schema

Read-onlyIdempotent

Retrieve an AI agent configuration schema and its current version by UUID to inspect or validate agent settings.

Instructions

Retrieve one agent configuration schema and its current version.

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": {
      "schema_id": "<schema_id>"
    },
    "name": "get_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
schema_idYesSchema UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.4
    • changedInput schema / properties / schema_id / description
      Previous value: -"UUID do schema"New value: +"Schema UUID"
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description contributes the useful detail that the result pairs the schema with its current version, but says nothing about error behavior for unknown UUIDs or whether a version history is included.

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?

One short sentence, front-loaded with the verb and resource, with zero filler or redundancy. Nothing could be removed without losing meaning.

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 tool with rich annotations and no output schema, the definition covers what it returns (schema plus current version) and what it needs (a schema UUID). Only the failure mode for a bad or missing identifier is left unstated, 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?

The single parameter is fully documented in the schema (UUID format, 'Schema UUID'), so the schema carries the load. The description adds no extra semantics about where to obtain the schema_id or what an invalid identifier produces, which is the baseline expectation at 100% coverage.

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 gives a specific verb (retrieve) and resource (agent configuration schema) plus scope ('one'), which clearly separates it from list-style or mutation siblings. It does not, however, distinguish it from other single-object getters such as get_version or get_snapshot, so an agent must infer the difference from the names alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as get_version for version-only lookups. The only implied context is that the caller already holds a schema UUID.

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