Skip to main content
Glama

Hal Fr Author

hal_fr_author
Read-onlyIdempotent

Author lookup (free-text query).

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": "Jean Dupont"
    },
    "name": "hal_fr_author"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsNo1-1000 (default 25).
queryYes

Output Schema

NameRequiredDescriptionDefault
responseNoAuthor search results
responseHeaderNoResponse metadata

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that: no matching behavior (fuzzy, prefix, exact), no indication of how results are ranked or limited, and no note that it queries an external open-world source.

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?

The definition is a single short sentence with zero waste and the resource is front-loaded. However, its brevity comes at the cost of under-specification rather than efficiency; there is no second sentence earning its place because no useful detail was included.

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?

An output schema exists, so return values need not be explained, but the description still omits what source is being searched, what kind of matching is performed, and how it relates to the closely named siblings. For an open-world lookup tool with a required free-text parameter, this leaves too much for the agent to infer.

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 coverage is 50%: the rows parameter is documented in the schema (1-1000, default 25) but query has only an example. The description's "free-text query" adds a small but real clarification that query is an unstructured string rather than an identifier, which is meaningful for a lookup tool.

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?

"Author lookup (free-text query)" names a resource (author) and a rough operation, so an agent can guess it finds author records from a text string. But it never states what an author record contains (IDs, names, affiliations) or how it differs from the sibling hal_fr_search, leaving the agent to infer the distinction from names alone.

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 at all: no statement of when an agent should pick this over hal_fr_search, hal_fr_get, or hal_fr_structure, and no prerequisites. The only implied usage comes from the words "author lookup," which an agent must interpret itself.

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.