SHVL

Find a customer or invoice

search_credit_control_cases

Read-onlyIdempotent

Search cases already held in the signed-in SHVL workspace by customer name or invoice reference. Read-only, account-scoped and capped at 20 results.

Input Schema

Name	Required	Description
`limit`	No	Maximum cases to return. Defaults to 10.
`query`	No	Optional customer-name or invoice-reference search.
`status`	No
`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
`cases`	Yes
`source`	Yes
`filters`	Yes
`case_count`	Yes
`data_notice`	Yes
`organisation`	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?

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description still adds the workspace scoping constraint and the 20-result cap, which an agent cannot derive from the annotations. Missing only whether results are ranked or paginated, which is minor given no pagination parameter exists.

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

Conciseness5/5

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

Two sentences, zero filler, with scope and search dimensions front-loaded before the read-only and result-cap qualifiers. Every clause carries information.

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?

An output schema exists, so return shape needn't be described, and the annotations cover the safety profile. For a simple four-parameter search tool the description is nearly sufficient; only the status filter's purpose is left unexplained.

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 75%, so the schema already documents workspace_id and limit well; the description merely echoes the 20-result cap that limit's maximum already enforces. The status filter is never mentioned in the description, leaving the agent to discover the enum values in 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?

States a specific verb and resource ('Search cases') plus the two searchable fields (customer name, invoice reference) and the scope ('the signed-in SHVL workspace'). This clearly separates it from get_credit_control_case, which fetches a single case, though the sibling is never named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Search cases already held in the signed-in SHVL workspace' implies the use case is lookup-by-name-or-reference, and 'account-scoped' signals a prerequisite. There is no explicit when-not guidance or pointer to get_credit_control_case for retrieving one case by id, so the routing is left to inference.

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?