Skip to main content
Glama
Sign In
reading-companion

reading-companion

by aby0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_author_profile

Retrieve or create an author profile to access books read, ratings, and notes for tracking reading progress.

Instructions

Get or create a profile for an author.

Args: author: Author name (e.g., "Leo Tolstoy")

Returns author data including books read, ratings, and notes.

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": "<author>"
    },
    "name": "get_author_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
authorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are present, so the description bears full burden. It mentions 'Get or create' but does not clarify whether creation is automatic, what happens if the author exists, or any side effects. Minimal behavioral context.

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 extremely concise, with the main purpose front-loaded. The docstring format for arguments and returns is efficient and wastes no words.

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?

For a simple tool with one parameter and no output schema, the description covers basic functionality. It mentions return fields (books read, ratings, notes) but lacks clarity on the creation aspect, which is important for completeness.

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?

The schema coverage is 0% but the description adds an example ('Leo Tolstoy') and clarifies that 'author' is the author's name. This adds some meaning beyond the schema, though more details (e.g., case sensitivity) would improve it.

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 'Get or create a profile for an author,' which clearly identifies the verb (get/create) and resource (author profile). However, it does not differentiate from sibling tools like 'get_profile' or 'get_favorite_authors', though the specificity to authors helps.

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?

No guidance is provided on when to use this tool versus alternatives such as 'get_profile' or 'save_profile'. It lacks information on prerequisites or preferred scenarios.

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

Deploy Server

Other Tools