Skip to main content
Glama

HelloBooks AI Agents MCP Server

how_munimji_helps

Read-only

Explain how HelloBooks and Munimji (the in-app AI assistant) help a specific business — given a free-text description of the user's own operations. Returns a curated capability knowledge base: business-operation areas (sales, purchases, banking, tax, reports, inventory, payroll, multi-entity, setup), and for each AI capability WHO does the work — autonomous (Munimji does it on its own, e.g. OCR extraction, running reports), approval (Munimji prepares the entry and you one-click approve before it posts to the ledger, e.g. AI categorization, find-and-match, creating invoices/bills by chat), assist (co-pilot, e.g. guided onboarding, voice), or manual (a software feature you run yourself). Each capability links to the backing software features. Use this when a user describes their business and asks "how can HelloBooks help me?", "what can the AI do for my shop/practice/agency?", or "what can Munimji do on its own vs what do I approve?". Pass their description in businessDescription; optionally filter by area or autonomy. The AI never posts to a ledger without approval. For the full software catalog call list_features; for pricing call list_plans.

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": "how_munimji_helps"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoOptional. Narrow to one business-operation area.
autonomyNoOptional. Filter Munimji capabilities by who does the work: `autonomous` (Munimji does it alone), `approval` (Munimji prepares, you approve before it posts), `assist` (co-pilot), `manual` (software feature you run yourself).
businessDescriptionNoOptional. The user describes their business and operations in their own words (industry, what they sell, how they get paid, who they pay, tax regime, pain points). It is echoed back as context — the calling assistant maps it to the returned areas + capabilities. No keyword scoring is done here; the LLM does the matching.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Consistent with readOnlyHint=true and openWorldHint=false: it is a pure knowledge-base read with no external effects. Beyond the annotations it discloses the return structure (areas, autonomy tier per capability, links to backing software features) and a substantive product constraint, "the AI never posts to a ledger without approval," which reframes how the approval tier should be interpreted. It omits edge behavior (what happens with no businessDescription, empty results), keeping it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded: what it does, then what it returns, then when to use, then how to call it. The autonomy taxonomy is restated nearly verbatim from the schema's enum description, which is some duplication, but it keeps the routing logic readable in one pass rather than splitting attention across fields.

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?

No output schema exists, so the description must carry the return shape — and it does, enumerating the ten operation areas and the four autonomy tiers with examples. Complete for correct invocation; only missing notes on degenerate inputs (vague or off-domain businessDescription) and result volume.

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 description coverage is 100% and both enums are documented in-schema, so baseline is 3. The description adds a usage instruction ("Pass their description in businessDescription; optionally filter by area or autonomy") and reinforces that matching is done by the calling LLM rather than keyword scoring, but it does not add syntax or format detail the schema lacks.

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?

A specific verb+resource: explains how HelloBooks and Munimji help a given business, returning a curated capability knowledge base keyed by operation area and autonomy mode. It explicitly distinguishes itself from siblings by naming list_features (full catalog) and list_plans (pricing), so an agent can route without opening schemas.

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?

Gives concrete trigger phrases ("how can HelloBooks help me?", "what can Munimji do on its own vs what do I approve?") plus the routing rules to list_features and list_plans. The when-to-use condition — user describes their business and asks about AI help — is unambiguous.

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.