Skip to main content
Glama
Sign In

robotbase-content

by io.github.wygogogo19
OverviewDiscussionsAdmin

Cyberlibrary Cite

cyberlibrary_cite
Read-onlyIdempotent

Ready-to-paste citation for one book: title, author, canonical page URL, Markdown URL, license and the public-domain territory notice. When to use: before quoting or summarising a book, so the answer carries a verifiable source. Do not use: to fetch content (use cyberlibrary_get_chapter). Returns: {title, author, page_url, markdown_url, license, source_url, citation, notice}.

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": {
      "lang": "<lang>",
      "slug": "<slug>"
    },
    "name": "cyberlibrary_cite"
  }
}

Input Schema

NameRequiredDescriptionDefault
langYes
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered structurally. The description adds useful context about what is returned (including a public-domain territory notice and license), but discloses nothing new about behavior beyond that – no auth needs, rate limits, or edge cases. A 3 is appropriate against a full annotation set.

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?

Front-loaded with the core purpose, then clearly subdivided into 'When to use', 'Do not use', and 'Returns'. Every clause earns its place with no 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?

For a read-only citation helper with no output schema, the description lists the return fields so the agent knows what it gets, and usage boundaries are clear. The only real gap is the undocumented lang/slug parameters, otherwise complete.

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 description coverage is 0% and the two required parameters (lang, slug) are documented nowhere. The description never explains what these identifiers mean or their expected format, so it fails to compensate for the coverage gap despite being the only source of parameter meaning.

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?

States a specific verb (cite) plus resource (one book) and enumerates the exact fields produced (title, author, page_url, license, notice). It also names the sibling it is not (cyberlibrary_get_chapter), so an agent can place it precisely among the ~60 tools.

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?

Explicitly gives both sides: 'When to use: before quoting or summarising a book, so the answer carries a verifiable source' and 'Do not use: to fetch content (use cyberlibrary_get_chapter)'. The alternative is named with the condition that selects it, leaving nothing to inference.

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

All robotbase-content 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