Skip to main content
Glama

Greenlit Books

by com.greenlitbooks
OverviewDiscussionsAdmin

Search the Greenlit Books catalog

search_greenlit_books
Read-onlyIdempotent

Ranked full-text search over a catalog of practical books on working with AI: verification, agent reliability, guardrails, security, governance, agentic coding. Returns scored results with title, description, series, and links. Follow a result's apiUrl or call get_book for the full record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesThe search query.
limitNoMax results, default 10.
seriesNoRestrict to one series.
audienceNoRestrict to one reader level.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / series / enum
      Previous value: -[
-  "the-operators-ai-library",
-  "the-ai-native-builder-canon",
-  "understand-and-trust-ai",
-  "build-agents-you-can-trust",
-  "lead-govern-and-apply-ai",
-  "ai-and-agentic-engineering",
-  "the-claude-code-ladder",
-  "the-agent-builders-workshop",
-  "the-two-doors",
-  "forward-deployed-engineering-handbooks",
-  "the-complete-grok-bot-guide",
-  "the-omarchy-books"
-]New value: +[
+  "the-operators-ai-library",
+  "the-ai-native-builder-canon",
+  "understand-and-trust-ai",
+  "build-agents-you-can-trust",
+  "lead-govern-and-apply-ai",
+  "ai-and-agentic-engineering",
+  "the-claude-code-ladder",
+  "the-agent-builders-workshop",
+  "the-two-doors",
+  "forward-deployed-engineering-handbooks",
+  "the-complete-grok-bot-guide",
+  "the-omarchy-books",
+  "the-personal-ai-computer"
+]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered. The description adds context beyond that: results are relevance-scored, and it enumerates the returned fields (title, description, series, links) plus the apiUrl follow-up path. It does not mention result caps or query behavior, but this is solid added value.

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 sentences, front-loaded with the core purpose, then the return shape, then the follow-up action. The topic enumeration is somewhat long but genuinely narrows the catalog scope. No filler or repetition.

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?

No output schema exists, yet the description discloses scoring and the returned fields, and it routes the agent to get_book/apiUrl for the full record. Given a 4-parameter, enum-constrained search tool, this is nearly complete; only pagination/ordering controls are unaddressed, and the sibling routing gaps keep it from a 5.

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%, covering q, limit (max 25, default 10), series, and audience, so the schema carries the parameter burden. The description only references 'series' incidentally as a returned field and adds no filtering syntax or semantics beyond the schema; baseline 3 applies.

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?

States a specific verb and resource ('ranked full-text search over a catalog of practical books') and scopes the domain with a concrete topic list (verification, guardrails, governance, agentic coding). It is clear what the tool does, but it never distinguishes itself from sibling search tools such as 'search' or 'find_books_for_topic', so the agent must infer which is appropriate.

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?

Provides follow-up routing ('Follow a result's apiUrl or call get_book for the full record'), which is real usage guidance for the next step. However it says nothing about when to choose this over the sibling 'search' or 'find_books_for_topic' tools, so selection guidance is only implied.

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

All Greenlit Books toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources