Skip to main content
Glama
Sign In
zoho-bookkeeper-mcp

zoho-bookkeeper-mcp

by bu5hm4nn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_expense_receipt

Read-only

Retrieve receipt or attachment details for a specific expense. Returns file information linked to the expense.

Instructions

Get receipt/attachment information for an expense. Returns details about any files attached to the expense.

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": {
      "expense_id": "<expense_id>"
    },
    "name": "get_expense_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
organization_idNoZoho org ID (uses ZOHO_ORGANIZATION_ID env var if not provided)
expense_idYesExpense ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the agent knows it's safe. The description adds that it returns 'details about any files attached,' which is minimal extra context beyond annotations. No contradictions.

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 short sentences that efficiently state purpose and what it returns. No redundant words. Front-loaded with the action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only 'get' tool with two parameters (one optional) and a clear purpose, the description is complete enough. It tells the agent what it does and what it returns, and sibling tools are diverse enough that the name and description suffice.

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 100% with both parameters well-described. The description adds no additional meaning beyond what the schema provides for parameters, so baseline score is appropriate.

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?

Clearly states it gets receipt/attachment information for an expense. The verb 'get' and resource 'expense receipt' are specific, and the name distinguishes from sibling tools like add_expense_receipt, delete_expense_receipt, and get_bill_attachment.

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?

No explicit guidance on when to use this tool vs alternatives. It is implied that it should be used when needing receipt info for an expense, but no exclusions or context for when to use other attachment getters (e.g., get_bill_attachment) is provided.

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