Skip to main content
Glama

Hal Fr Search

hal_fr_search
Read-onlyIdempotent

Solr-style search across HAL.

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": {
      "query": "title_t:transformer"
    },
    "name": "hal_fr_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
flNoComma-sep fields to return.
fqNoSolr filter query.
rowsNo1-10000 (default 25).
sortNoe.g. "submittedDate_tdate desc"
queryYesFree-text or Solr query (e.g. "title_t:transformer").
startNo0-based offset.

Output Schema

NameRequiredDescriptionDefault
responseNoSearch results
responseHeaderNoResponse metadata

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The only added signal is "Solr-style", which hints at the query dialect but gives no detail on limits (e.g. row caps, pagination cost, whether fq is ANDed). An output schema exists, so return-shape disclosure is not required.

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

Conciseness3/5

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

Six words with zero padding, so nothing is wasted, but the brevity comes at the cost of substance rather than from disciplined editing. It is front-loaded but under-delivers for a tool with a full Solr query DSL.

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?

This is a six-parameter search tool exposing a Solr dialect, yet the description never explains what HAL contains, what fields are searchable, or how it relates to the sibling hal_fr_* tools. Rich annotations and an output schema reduce the burden, but the routing and query-language gaps remain significant.

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 every parameter including fl, fq, rows, sort, start and query is already documented in the schema. The description adds nothing beyond implying Solr query syntax, which the schema already illustrates via examples; baseline 3 applies.

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?

States a verb and resource ("search across HAL") and distinguishes the query dialect ("Solr-style"), but HAL is never expanded and the scope of the search is left vague. It gives no basis for telling this apart from siblings like hal_fr_get or hal_fr_author beyond the word 'search'.

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 when-to-use guidance, no prerequisites, and no mention of any alternative tool. An agent must guess whether to reach for this or hal_fr_author/hal_fr_structure when looking for a person or structure record.

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.