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 (a bank proposal the review row shows differently — an OWNER_WITHDRAWAL the loan fence places as LOAN_PAYMENT or OTHER — also carries shownOnReviewAs {category, reason}); (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.

  1. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "expense",
      -  "invoice",
      -  "bill",
      -  "quote",
      -  "receipt",
      -  "payment",
      -  "contact",
      -  "contact_update",
      -  "employee_update",
      -  "product_update",
      -  "recurring",
      -  "credit_note",
      -  "debit_note",
      -  "purchase_order",
      -  "journal",
      -  "invoice_update",
      -  "bill_update",
      -  "logo_update",
      -  "quote_update",
      -  "delivery_order_update",
      -  "purchase_order_update",
      -  "credit_note_update",
      -  "supplier_debit_note_update",
      -  "expense_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",
      +  "bill_update",
      +  "logo_update",
      +  "quote_update",
      +  "delivery_order_update",
      +  "purchase_order_update",
      +  "credit_note_update",
      +  "supplier_debit_note_update",
      +  "expense_update",
      +  "bank_clearing",
      +  "payment_match",
      +  "bank",
      +  "staged_documents",
      +  "staged_balances",
      +  "staged_master"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous 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"
      -]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",
      +  "bill_update",
      +  "logo_update",
      +  "quote_update",
      +  "delivery_order_update",
      +  "purchase_order_update",
      +  "credit_note_update",
      +  "supplier_debit_note_update",
      +  "expense_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",
      -  "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"
      +]
  4. 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"
      +]
  5. 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"
      +]
  6. 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"
      +]
  7. 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"
      +]
  8. Added

TDQS

A3.6/5.0
Behavior1/5

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

The description emphatically declares 'READ-ONLY. It changes nothing', yet the annotations set readOnlyHint=false, which asserts the tool is not read-only. This is a direct contradiction on the safety-relevant dimension an agent weighs most before calling. Other useful disclosures (truncation reporting, null reason semantics) cannot offset a conflicting safety claim.

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 four numbered buckets give it real structure and the purpose is front-loaded, but it is a single ~250-word paragraph with rhetorical asides ('that one is now invoice INV-0042', 'READ IT and fix precisely'). Several lines serve post-call behavior rather than invocation, making it heavier than needed.

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?

With no output schema and no schema descriptions, the description carries the return-shape burden well: it names per-item fields (reference, party, amount, days waited, next step, review link, shownOnReviewAs, reason/reasonRecorded) and the STAGED/APPROVED semantics. Coverage is strong, though the kind enum and the limit maximum discrepancy leave small gaps.

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?

With 0% schema description coverage, the description must compensate and largely does: it gives `since` as YYYY-MM-DD or ISO with a 7-day default, `kind` as a single-lane filter, and `limit` default 50 with honest truncation reporting. It omits that `limit`'s stated max of 200 conflicts with the schema's far larger maximum, and it never lists the `kind` enum values, so it is not fully self-sufficient.

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?

Names the specific resource ('YOUR OWN QUEUE in this company') and enumerates exactly what it returns across four buckets (PENDING, APPROVED, REJECTED, STAGED), which distinguishes it from siblings like search_documents, open_invoices, or bank_review_queue. An agent can tell what this tool uniquely provides 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?

Usage is clearly framed as a personal queue read that answers four concrete questions, and it explicitly rules out approval/money-movement actions ('no tool can approve... every pending item is one human tap'). It does not, however, name a sibling alternative or state when a different tool would be preferable.

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