Skip to main content
Glama

boundaries

Read-onlyIdempotent

Check architecture layer violations, such as domain importing infrastructure, for a module or entire codebase to enforce clean layer separation.

Instructions

Check architecture layer violations (e.g. domain importing infrastructure) for one module or all.

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

Input Schema

NameRequiredDescriptionDefault
allNoList everything instead of stopping at 200 items.
scopeNoModule ID or "all".all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered without the description. The description adds no further behavioral context — nothing about what a violation report looks like, whether checks are cached, or how the 200-item truncation interacts with results — so it is only minimally viable on this dimension.

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?

A single front-loaded sentence with zero filler; the parenthetical example does real work by defining what a 'layer violation' means. Nothing is padded or repeated.

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?

There is no output schema, yet the description says nothing about the shape of the result — per-violation entries, severity, file locations, or how truncation surfaces. It also leaves the relationship to sibling analysis tools unexplained, so an agent has enough to call it but not full confidence it is the right choice.

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%, so both 'scope' (module ID or "all") and 'all' (list everything vs. stop at 200) are already documented in the schema. The phrase 'one module or all' merely restates the scope parameter and adds no format or syntax detail beyond it, making the baseline 3 correct.

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?

States a specific verb and resource ('Check architecture layer violations') and grounds it with a concrete example (domain importing infrastructure) plus its coverage scope (one module or all). It does not, however, distinguish itself from plausible siblings such as 'layers' or 'boundary', so an agent must infer the split.

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?

'For one module or all' implies the scoping choice but gives no explicit when-to-use rule and no exclusion pointing at another tool. An agent knows roughly what the tool does but not why it would prefer it over the boundary/layers siblings.

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