SHVL

See which overdue invoices need attention

get_credit_control_brief

Read-onlyIdempotent

Use when someone asks who owes money, which invoices are overdue or which customers need a payment reminder. Return the selected business's overdue totals and up to five customers to check first. Read-only. Uses the latest SHVL import or completed accounting sync and never sends a reminder.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum priority cases to return. Defaults to 5.
`workspace_id`	Yes	Exact workspace_id returned by list_shvl_workspaces and selected by the user. Never infer a different client workspace.

Output Schema

Name	Required	Description	Default
`source`	Yes
`summary`	Yes
`data_notice`	Yes
`generated_at`	Yes
`organisation`	Yes
`priority_cases`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 3, 2026

addedInput schema / properties / workspace_id

Added value: +{
+  "description": "Exact workspace_id returned by list_shvl_workspaces and selected by the user. Never infer a different client workspace.",
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "workspace_id"
+]
```

First observedOct 17, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety bar is low. The description still adds real value by naming the data source ('latest SHVL import or completed accounting sync') and stating 'never sends a reminder', which pre-empts the most likely misread of a payment-reminder tool.

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?

Three sentences, front-loaded with the trigger and with zero filler, which is well structured. It is on the shorter side for a tool with a freshness caveat, so the tightness slightly trades off completeness.

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 an output schema present, return values need not be explained, and the description covers scope, data freshness and the read-only guarantee. Only edge behavior — such as what returns when no import or sync has completed — is unaddressed.

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, including the limit maximum of 5 and the workspace_id sourcing rule. The description reinforces the cap ('up to five customers') and frames results as priority cases, but adds no syntax or sourcing detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a concrete verb and resource: return overdue totals plus up to five customers to check first. That is specific enough to separate it from get_receivables_health and analyse_aged_debtors_csv, though it never names a sibling to distinguish itself explicitly.

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 trigger phrasing ('Use when someone asks who owes money, which invoices are overdue or which customers need a payment reminder'), which is stronger than most definitions. It stops short of naming which sibling to prefer for narrower questions like a single case or an aged-debtor CSV.

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

All SHVL tools Inspect

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

Need Help?