Skip to main content
Glama

docs-get_hla

Retrieve the High-Level Architecture document from exeris-docs to read the canonical narrative of the three-tier model.

Instructions

Fetch the High-Level Architecture document (high-level-architecture.md) from exeris-docs. Canonical narrative of the three-tier model.

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": "docs-get_hla"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, and it discloses little beyond the identity of the file. It does not state failure behavior if the document is absent, the format/size of the returned content, or that it is a side-effect-free read; for a zero-parameter fetch the risk is low, but the behavioral disclosure is thin.

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 padding, and the identity of the fetched document is front-loaded before the characterization of its content. Nothing is wasted.

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 zero-parameter, no-output-schema fetch of a single named file, the description gives enough to select and call it correctly, and the .md name implies the return format. Only the failure/absence behavior and content shape remain unspecified, which is a minor gap at this complexity level.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly signals that no input is needed by naming the specific document as fixed.

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: it fetches the High-Level Architecture document, naming the exact file (high-level-architecture.md) and its source (exeris-docs). That filename-level specificity implicitly separates it from siblings like docs-get_adr, docs-get_whitepaper, and docs-get_repo_doc, though no sibling is named explicitly.

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 only implied: an agent can infer it should call this to read the architecture narrative, reinforced by the phrase 'canonical narrative of the three-tier model'. There is no explicit when-to-use or when-not-to-use guidance, and no routing away from the other get_* tools for overlapping documentation needs.

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