Skip to main content
Glama

get_base_constraints

Retrieve immutable base constraints that all protocols must comply with to enforce security boundaries that cannot be overridden.

Instructions

Get the immutable base constraints that all protocols must comply with. These define security boundaries that cannot be overridden.

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": {
      "projectDir": "<projectDir>"
    },
    "name": "get_base_constraints"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format (default: pretty)
projectDirYesAbsolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose meaningful behavior: the returned constraints are immutable and non-overridable security boundaries, which tells an agent these are authoritative read-only reference data. It does not state the return shape, whether constraints are grouped by category, or any file/permission prerequisites for reading from projectDir.

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 short sentences with zero filler, and the core identity of the resource is front-loaded before the immutability qualifier. 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 two-parameter read tool with fully documented schema and no output schema, the definition covers what the tool fetches and why it matters. The main residual gap is that the description gives no hint about the structure or volume of the returned constraint set.

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%, with both projectDir and format fully documented including the enum values and default, so the schema already handles parameter meaning. The description adds nothing about what the format options produce (e.g., how compact differs from json), so the 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?

The description uses a specific verb ("Get") and resource ("base constraints") and further qualifies them as immutable safety restrictions, so an agent knows this retrieves policy statements rather than records or logs. It does not explicitly contrast itself with siblings like get_violations or get_audit_log, so sibling differentiation is implied rather than stated.

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?

Phrases like "that all protocols must comply with" and "cannot be overridden" imply the context in which the tool is relevant (before or while defining/inspecting a protocol), but there is no explicit when-to-use instruction and no exclusion pointing an agent to a different tool for related data. Usage is inferable but not guided.

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