Skip to main content
Glama

Taokeh MCP server

My work

my_work

YOUR OWN QUEUE in this company, in one call — what you filed and what happened to it. Answers four questions: (1) PENDING — everything of yours still waiting on the owner's approval, across every lane (expense, invoice, bill, quote, receipt, supplier payment, contact, credit note, debit note, purchase order, adjusting journal, your bank-category proposals), each with its reference, party, amount, how many days it has waited, and the exact next step in words plus the owner's review link; (2) APPROVED — what the owner approved since since (default: the last 7 days) and WHAT IT BECAME, with the posted document's own reference, so you can say "that one is now invoice INV-0042"; (3) REJECTED — what the owner or the engine refused, with the reason VERBATIM whenever one is stored. Every reject door in Taokeh offers the owner an optional "Why?" box, and staged migration rows carry the engine's own refusal text; where a reason is present, reason holds those exact words and reasonRecorded is true — READ IT and fix precisely what it names rather than re-filing the same thing. The box is never compulsory, so a refusal with an empty box reports reason: null and reasonRecorded: false; read that as "unknown", ask the owner what was wrong, and do NOT guess why before re-filing; (4) STAGED — your migration work (historical documents, opening balances, master data) sitting at a commit door. Params: since (YYYY-MM-DD or ISO, optional), kind (optional single-lane filter), limit (default 50, max 200 — every bucket reports total, returned and an honest truncation note; nothing is silently dropped). READ-ONLY. It changes nothing, it cannot approve anything, no tool can approve on the owner's behalf, and no tool of any kind moves money — every pending item is one human tap in Taokeh.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNo
limitNo
sinceNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "expense",
      -  "invoice",
      -  "bill",
      -  "quote",
      -  "receipt",
      -  "contact",
      -  "contact_update",
      -  "employee_update",
      -  "product_update",
      -  "recurring",
      -  "credit_note",
      -  "debit_note",
      -  "purchase_order",
      -  "journal",
      -  "invoice_update",
      -  "logo_update",
      -  "bank",
      -  "staged_documents",
      -  "staged_balances",
      -  "staged_master"
      -]New value: +[
      +  "expense",
      +  "invoice",
      +  "bill",
      +  "quote",
      +  "receipt",
      +  "payment",
      +  "contact",
      +  "contact_update",
      +  "employee_update",
      +  "product_update",
      +  "recurring",
      +  "credit_note",
      +  "debit_note",
      +  "purchase_order",
      +  "journal",
      +  "invoice_update",
      +  "logo_update",
      +  "bank",
      +  "staged_documents",
      +  "staged_balances",
      +  "staged_master"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "expense",
      -  "invoice",
      -  "bill",
      -  "quote",
      -  "receipt",
      -  "contact",
      -  "contact_update",
      -  "employee_update",
      -  "product_update",
      -  "recurring",
      -  "credit_note",
      -  "debit_note",
      -  "purchase_order",
      -  "journal",
      -  "invoice_update",
      -  "bank",
      -  "staged_documents",
      -  "staged_balances",
      -  "staged_master"
      -]New value: +[
      +  "expense",
      +  "invoice",
      +  "bill",
      +  "quote",
      +  "receipt",
      +  "contact",
      +  "contact_update",
      +  "employee_update",
      +  "product_update",
      +  "recurring",
      +  "credit_note",
      +  "debit_note",
      +  "purchase_order",
      +  "journal",
      +  "invoice_update",
      +  "logo_update",
      +  "bank",
      +  "staged_documents",
      +  "staged_balances",
      +  "staged_master"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "expense",
      -  "invoice",
      -  "bill",
      -  "quote",
      -  "receipt",
      -  "contact",
      -  "contact_update",
      -  "employee_update",
      -  "product_update",
      -  "recurring",
      -  "credit_note",
      -  "debit_note",
      -  "purchase_order",
      -  "journal",
      -  "bank",
      -  "staged_documents",
      -  "staged_balances",
      -  "staged_master"
      -]New value: +[
      +  "expense",
      +  "invoice",
      +  "bill",
      +  "quote",
      +  "receipt",
      +  "contact",
      +  "contact_update",
      +  "employee_update",
      +  "product_update",
      +  "recurring",
      +  "credit_note",
      +  "debit_note",
      +  "purchase_order",
      +  "journal",
      +  "invoice_update",
      +  "bank",
      +  "staged_documents",
      +  "staged_balances",
      +  "staged_master"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "expense",
      -  "invoice",
      -  "bill",
      -  "quote",
      -  "receipt",
      -  "contact",
      -  "contact_update",
      -  "credit_note",
      -  "debit_note",
      -  "purchase_order",
      -  "journal",
      -  "bank",
      -  "staged_documents",
      -  "staged_balances",
      -  "staged_master"
      -]New value: +[
      +  "expense",
      +  "invoice",
      +  "bill",
      +  "quote",
      +  "receipt",
      +  "contact",
      +  "contact_update",
      +  "employee_update",
      +  "product_update",
      +  "recurring",
      +  "credit_note",
      +  "debit_note",
      +  "purchase_order",
      +  "journal",
      +  "bank",
      +  "staged_documents",
      +  "staged_balances",
      +  "staged_master"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "expense",
      -  "invoice",
      -  "bill",
      -  "quote",
      -  "receipt",
      -  "contact",
      -  "credit_note",
      -  "debit_note",
      -  "purchase_order",
      -  "journal",
      -  "bank",
      -  "staged_documents",
      -  "staged_balances",
      -  "staged_master"
      -]New value: +[
      +  "expense",
      +  "invoice",
      +  "bill",
      +  "quote",
      +  "receipt",
      +  "contact",
      +  "contact_update",
      +  "credit_note",
      +  "debit_note",
      +  "purchase_order",
      +  "journal",
      +  "bank",
      +  "staged_documents",
      +  "staged_balances",
      +  "staged_master"
      +]
  6. Added

TDQS

A3.8/5.0
Behavior1/5

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

The description explicitly claims "READ-ONLY. It changes nothing," but the annotations set readOnlyHint to false. This is a direct contradiction between the descriptive text and structured metadata. Per the rubric, a contradiction forces a score of 1, despite the description otherwise containing rich behavioral detail.

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

Conciseness3/5

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

The description is front-loaded with core purpose and uses numbered sections, which is good structure. However, it is verbose and repetitive, repeating the read-only point multiple times ("READ-ONLY", "It changes nothing", "it cannot approve anything", "no tool can approve on the owner's behalf"). It would benefit from tightening.

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 tool with no output schema, the description thoroughly explains what will be returned in each bucket: pending items with reference, party, amount, wait time, next step, and review link; approved items with the resulting posted document reference; rejected items with verbatim reasons and `reasonRecorded` semantics; and staged migration work. It leaves no critical operational gap.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates: it specifies `since` as YYYY-MM-DD or ISO with a 7-day default, `kind` as an optional single-lane filter, and `limit` with default 50, max 200, and honest truncation behavior. It adds practical meaning that the sparse schema alone does not provide.

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 opens with a specific, concrete purpose: "YOUR OWN QUEUE in this company, in one call — what you filed and what happened to it." It enumerates four distinct status questions (PENDING, APPROVED, REJECTED, STAGED), making the tool's role unmistakable and distinguishing it from sibling report/review tools.

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?

It gives clear context for when to use the tool: the user wants one consolidated view of their own filed items across all lanes, including approvals since a date and migration items. It does not explicitly name alternatives or exclusion conditions (e.g., 'use bank_review_queue instead when...'), so it stops short of a 5.

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