Skip to main content
Glama

Hal Fr Get

hal_fr_get
Read-onlyIdempotent

Single document by HAL id.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hal_id": "hal-01234567"
    },
    "name": "hal_fr_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
hal_idYes

Output Schema

NameRequiredDescriptionDefault
responseNoSearch results
responseHeaderNoResponse metadata

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered structurally. The description adds no behavioral context at all — nothing about failure on unknown ids, auth, or rate limits — so it contributes nothing beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single five-word fragment, front-loaded with the resource and the key. It wastes nothing, though the terseness borders on under-specification rather than disciplined brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

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

The tool is simple (one required param, output schema present), which lowers the bar, but the description still leaves an agent without any sense of what the returned document contains or how it relates to the sibling search/author/structure tools.

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?

Only one parameter exists and its schema description coverage is 0%, but the description names it ("by HAL id") and the schema supplies an example value ("hal-01234567"). The description confirms the id identifies the document but adds no format or validation details beyond the schema's example.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Single document by HAL id" names the resource (one document) and the lookup key, and the word "single" implicitly contrasts with a multi-result search sibling. However, it never says what a HAL document is or what retrieving it entails, so the purpose is only minimally viable.

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 explicit when-to-use guidance, no statement of when to prefer hal_fr_search or hal_fr_structure instead, and no prerequisites. The agent must infer the routing from the word "single" alone.

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.