Skip to main content
Glama

list_authors

Check which women authors are represented in the curated corpus by name, including counts of works, passages, and curated items. Filter by name substring to see if a specific author exists.

Instructions

Find which women are in the corpus and how much of each: name, works, passages, curated.

Use when the user asks 'is X in there?' or 'who do you have on Y?'. Not a
passage search — pair with search_corpus once you know the name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryNoSubstring of a name. Unset lists the most represented authors.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
statusYesok — passages found that match most of the question's terms. weak — something matched, but thinly; say so if you use it. no_coverage — the corpus does not speak to this. Say that. Do not answer from elsewhere. not_found — a specific reference did not resolve.
constraintNoAnswer only from these passages. Quote or closely paraphrase, and cite each claim as [Author, Title §n]. If the passages do not speak to the question, say so plainly rather than filling the gap from elsewhere.
provenanceNoEvery passage is from a work by a named woman author. Each hit's `source` says where that text came from and on what basis; `curated` says whether a person reviewed the edition.
limitationsNoPart of the answer, not a disclaimer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.2

TDQS

A3.9/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. It states the tool 'finds' and lists aspects, but does not disclose whether it is read-only, any side effects, sorting behavior, pagination, or auth requirements. This is a meaningful gap for a tool that could be mistaken for a mutation or complex operation.

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?

The description is two sentences and a brief 'not' clause, front-loading the purpose and usage. Every sentence earns its place, with no redundant wording or filler.

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?

Given that an output schema exists (indicated in context), the description need not explain return values. It covers purpose, usage, and exclusions adequately. Minor omissions like sorting or limit semantics are acceptable given the output schema and concise scope.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% (query has a description, limit does not). The description adds no parameter information beyond what the schema already provides. It does not explain how limit interacts with the query or how results are ordered, so it fails to compensate for the gap.

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

Purpose5/5

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

The description clearly states the verb (Find), the resource (which women are in the corpus), and the specific dimensions (name, works, passages, curated). It also differentiates itself from sibling tools by explicitly noting it is not a passage search and directing to search_corpus.

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

Usage Guidelines5/5

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

Provides explicit when-to-use triggers ('is X in there?' or 'who do you have on Y?') and an explicit exclusion with an alternative ('Not a passage search — pair with search_corpus once you know the name'). This leaves no ambiguity about when to select this tool.

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