Skip to main content
Glama

region_spec_schema

Provides the JSON Schema and field meanings for RegionSpec inputs accepted by build_region, helping you create valid region specifications.

Instructions

JSON Schema of the RegionSpec that build_region takes (field meanings included).

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": "region_spec_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool returns a JSON Schema and that field meanings are included, which is useful, but it does not explicitly state that the operation is read-only, has no side effects, or clarify the complete return structure beyond 'JSON Schema'.

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?

The description is a single front-loaded sentence with no wasted words. It establishes the resource, its relation to build_region, and the inclusion of field meanings.

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 simple zero-parameter schema introspection tool, the description is largely complete: it says what schema is returned and why it is relevant to build_region. A little more context about the read-only nature or how thoroughly the RegionSpec is covered would make it fully complete, especially since there is no output schema.

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?

The tool takes zero parameters, so the baseline is 4. There are no parameter semantics that the description needs to add.

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 names a specific artifact (the JSON Schema of RegionSpec) and ties it directly to build_region. It clearly distinguishes this schema lookup tool from build_region itself, though it does not use an explicit verb like 'return' or 'describe'.

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?

Usage is implied: an agent should call this to learn the RegionSpec fields that build_region accepts. However, there is no explicit statement of when to use this instead of calling build_region, nor any prerequisites or exclusions.

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