Skip to main content
Glama
Sign In

YESbusiness

by ch.yesbusiness
OverviewDiscussionsAdmin

Documents without a booking

list_unattached_documents
Read-onlyIdempotent

The company's documents (receipts, supplier invoices, statements) that NO booking holds yet, newest first: id, file_name, mime, size_bytes, uploaded_on, external_link (true = a link to a file stored elsewhere, nothing to read). Use it when the user has put invoices into YESbusiness Documents and asks you to match them to bank transactions: read a candidate with get_document (its signed_url, not inline base64, unless the file is small), then pass its id in documents_ids on propose_bank_transaction_booking or propose_booking. search narrows by file name. Only available when the connection was granted access to files.

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": {
      "company_id": "<company_id>"
    },
    "name": "list_unattached_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoText the file name must contain.
company_idYesThe company to work on — one of list_my_companies' company_id values.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses return ordering, the returned field set, and the non-obvious meaning of external_link (a pointer to a file stored elsewhere, nothing to read). It also surfaces an availability prerequisite — the connection must have been granted file access — which annotations cannot express.

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-loads what the list contains and its scope before moving into the workflow and caveats, with no filler sentences. It is dense — a single long block chaining scope, field list, workflow, and access gating — which is slightly harder to scan than it could be.

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?

There is no output schema, and the description compensates by enumerating the returned fields and their meaning, plus ordering. Combined with the workflow and access condition, an agent has everything needed to call this correctly against a 2-parameter read tool.

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%, so both parameters are already documented and the baseline is 3. The description only restates that search narrows by file name, adding no format, matching, or edge-case detail beyond 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?

States a specific resource (company documents: receipts, supplier invoices, statements) with an explicit scope qualifier (documents NO booking holds yet) and ordering (newest first). This clearly separates it from siblings like list_bookings and get_document without needing to open a schema.

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 an explicit triggering scenario (user uploaded invoices and wants them matched to bank transactions) and a concrete follow-up sequence: read a candidate with get_document, then pass its id in documents_ids on propose_bank_transaction_booking or propose_booking. It also names search as the narrowing mechanism, leaving little to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All YESbusiness toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources