Skip to main content
Glama

List Author Directions

get_author_directions
Read-onlyIdempotent

List the research directions an author publishes in and check whether they are active in a given area. Provide an author ID or URL to retrieve paginated results.

Instructions

List the research directions one author publishes in, one page at a time.

Use for "what areas does X work in" or to check whether a person is active in a given direction. Pass an author id or URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "author_id_or_url": "<author_id_or_url>"
    },
    "name": "get_author_directions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
author_id_or_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld behavior, so the safety profile is covered. The description adds pagination ('one page at a time') but does not describe ordering, page size behavior, or what happens on an unknown author except via the output schema. It adds modest value 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?

Three short sentences, front-loaded with the core purpose and followed by when-to-use and the input note. No filler, though the line breaks fragment the phrasing slightly without loss of meaning.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. However, for a paginated tool with zero schema descriptions, the lack of any guidance on limit/offset semantics (default page size, how to iterate) leaves a real gap for correct invocation.

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 0%, so the description must compensate, and it only does so partially: it says to pass an author id or URL, clarifying the accepted input forms, but it never explains limit or offset despite pagination being mentioned. The required parameter is addressed, the two paging parameters are not.

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?

The description states a concrete verb and resource: 'List the research directions one author publishes in, one page at a time,' which is distinct from siblings like get_author_papers and get_author_context. It does not explicitly contrast itself with those siblings, so this falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete triggering phrases ('what areas does X work in', checking whether a person is active in a direction) and a usage constraint ('Pass an author id or URL'). No explicit exclusions or named alternatives are given, so it is clear context without full routing guidance.

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