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

zoho-bookkeeper-mcp

by bu5hm4nn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_organization

Read-only

Retrieve detailed information about an organization, including address, contact details, and settings.

Instructions

Get detailed information about a specific organization. Returns full organization details including address, contact info, and settings.

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_organization"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=true and openWorldHint=true. The description adds specific details about the return content (address, contact info, settings) beyond what annotations convey, which is valuable for understanding the tool's behavior.

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 two sentences with no wasted words. It front-loads the key action and then specifies return fields. Every sentence adds value.

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 get tool with a single optional parameter and good annotations, the description adequately explains the return content (address, contact info, settings) despite no output schema. No missing context.

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?

With 100% schema description coverage, the schema already documents the parameter well. The description does not add any additional meaning or syntax guidance beyond what is in the schema.

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?

The description clearly states 'Get detailed information about a specific organization', specifying the verb and resource. It distinguishes from sibling tools like list_organizations (which lists multiple) and other get tools for different entities.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives, nor when not to use it. Usage is implied by the name and context, but no exclusions or alternative suggestions are given.

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