Skip to main content
Glama

Tokenbooks - crypto and fiat accounting and payments

Get Help

get_help
Read-onlyIdempotent

Find practical Tokenbooks instructions or accounting guidance. Pass query to search by topic (MCP workflow, cost basis, fair market value, gas fees, stablecoins, ...), or pass a slug from a previous search result to open that article.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_help"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoHelp article slug to open directly, from a previous get_help search result. Omit when using query.
limitNoMaximum number of search results, only used with query
queryNoSearch query for Tokenbooks instructions or accounting guidance. Omit when using slug.

Output Schema

NameRequiredDescriptionDefault
bodyNo
slugNo
tagsNo
errorNo
queryNo
titleNo
messageNo
resultsNo
summaryNo
audienceNo
relatedToolsNo
relatedConceptsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld=false, so the safety profile is fully covered by structured data. The description adds the search-then-open workflow, but does not say what happens when neither parameter is supplied, when both are supplied, or how limit affects direct slug opens. Useful but thin beyond the annotations.

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?

Two sentences with no filler, front-loaded with the purpose and then enumerating the two mutually exclusive modes. The parenthetical topic list is compact and directly actionable.

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, zero-required-parameter help tool with an output schema, the description covers purpose, both modes, and query vocabulary. The remaining gap is sibling disambiguation and no-argument behavior, minor for a tool this simple.

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

Parameters4/5

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

Schema coverage is 100% so baseline is 3, but the description earns an extra point by giving concrete query topics (MCP workflow, cost basis, fair market value, gas fees, stablecoins) that tell the agent how to phrase searches far better than the schema's generic "Search query for Tokenbooks instructions". It adds nothing about limit, which the schema already handles.

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 and resource ("Find practical Tokenbooks instructions or accounting guidance") and immediately distinguishes its two operating modes: topical search via query, or direct article open via slug. An agent knows exactly what the tool returns conceptually 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 Guidelines4/5

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

Gives clear mode-selection guidance: pass query to search by topic, pass slug (from a previous search result) to open an article. What is missing is routing against a close sibling such as get_accounting_reference or get_server_info — an agent could plausibly reach for the wrong one when it wants accounting rules rather than prose help.

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