Skip to main content
Glama

literary-agent-scout

Literary Agent Scout: quoted wish-list matches with query status and fee checks — For an author with a book to query, finds literary agents and agencies on the agencies' own websites, reads their guidelines and agent bios, and ranks them against your pitch. Every fit claim carries a sentence quoted verbatim from the agent's page (quotes not found on the page are dropped), each agent shows whether the page says queries are open or closed with the retrieval time, and any agency p

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": {
      "manuscript": "<manuscript>"
    },
    "name": "literary-agent-scout"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesNoAgency submission, wish-list or agent-bio pages you already found. They are read and checked like the ones found by search.
discoverNoSearch the web for more agencies (default true). Set false to check only the pages you supplied.
manuscriptYes
max_resultsNoDefault 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does much of it: it discloses that every fit claim must carry a verbatim quote, that unverifiable quotes are dropped, that query open/closed status and retrieval time are surfaced, and that fee checks are performed. It omits that the tool reads the public web (network access implied but not stated as a constraint) and the trailing sentence is cut off mid-clause ('and any agency p'), so the fee-check promise is left unfinished.

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 front-loaded framing is good and each clause adds information, but the sentences are extremely dense and the definition ends abruptly mid-word, leaving the final guarantee dangling. The title restatement prefix is slightly wasteful, though the subtitle that follows earns its place.

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?

There is no output schema, and the description compensates well by describing the shape of results: quoted evidence per fit claim, query status, and retrieval timestamps. What is missing is coverage of the input-side choices (search vs supplied pages, result caps of 8) for a tool with a nested object and four parameters.

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 75%, so the schema already documents most inputs including the nested manuscript object. The description adds only 'against your pitch', saying nothing about `pages`, `discover`, or `max_results`, so it does not raise the bar above the schema baseline.

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 names a specific verb and resource chain: finds literary agents and agencies on their own sites, reads guideline and bio pages, and ranks them against the pitch. The audience and trigger ('For an author with a book to query') are stated up front, so the agent knows exactly what this tool is for without opening the schema.

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

Usage Guidelines3/5

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

The intended use case is clear from 'For an author with a book to query', but there is no explicit when-not guidance and no named alternative. The schema's `discover` flag (search the web vs check only supplied pages) is a real routing decision that the description never mentions, leaving the agent to infer it.

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.

Resources