Skip to main content
Glama

Get saved layout

get_schema
Read-onlyIdempotent

Read one saved extraction layout by slug.

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

Input Schema

NameRequiredDescriptionDefault
slugYesStable id: lowercase letters, digits, underscores (hyphens accepted, stored as underscores).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / name
      Removed value: -{
      -  "description": "Lowercase letters, digits, underscores, and hyphens. No spaces.",
      -  "maxLength": 80,
      -  "minLength": 1,
      -  "pattern": "^[a-z0-9_-]+$",
      -  "type": "string"
      -}
    • addedInput schema / properties / slug
      Added value: +{
      +  "description": "Stable id: lowercase letters, digits, underscores (hyphens accepted, stored as underscores).",
      +  "maxLength": 80,
      +  "minLength": 1,
      +  "pattern": "^[a-z0-9_-]+$",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "name"
      -]New value: +[
      +  "slug"
      +]
  2. First observed

TDQS

B3.1/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is fully covered elsewhere. The description adds nothing beyond that profile — it does not say what happens when the slug is unknown (error vs. empty), whether reads are cached, or anything about the returned layout. It largely restates the title.

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. 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.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with rich annotations and a fully documented schema, the definition is serviceable but thin. With no output schema, the description should hint at what a layout read returns or what a missing slug produces; neither is covered.

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%, and the schema itself explains the slug format, casing, hyphen-to-underscore normalization, and length bounds. The description only confirms that slug is the lookup key, so the schema does the heavy lifting; baseline 3 applies.

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?

"Read one saved extraction layout by slug" gives a concrete verb (read), a bounded resource (one saved extraction layout), and the lookup key. An agent can distinguish it from list_schemas or create_schema. It loses a point for terminology drift: the tool is named get_schema and its parameter is slug, but the description calls the resource a "layout" without bridging the two terms.

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 when-to-use guidance and no reference to any sibling. The description never says to use list_schemas to discover slugs or create_schema when the slug does not exist, so the agent must infer routing on its own.

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.

Resources