Skip to main content
Glama

Kunden suchen

search_clients
Read-onlyIdempotent

Find clients of the connected facturo account by name (typos and partial names are fine) or city; an empty query lists everyone. Call it before previewing for a client that may already exist and pass the client_id to preview_invoice. 'match' is 'exact', 'candidates' (one candidate: use it and name it; several: ask the user which one), 'none' (a new client) or 'all'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_clients"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoName, part of a name, or city

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes further by disclosing matching behavior (typos and partial names accepted, empty query returns everyone) and the semantics of the returned 'match' field. With no output schema, that return-value interpretation is exactly the context an agent cannot get elsewhere.

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?

Purpose is front-loaded, followed by the workflow hook and then the 'match' enumeration; no sentence is filler. The final sentence is dense with embedded quoting and parentheses, which is slightly harder to parse than it needs to be, but nothing is redundant.

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 one-parameter read tool with no output schema, the description supplies what is missing: how results should be interpreted via 'match' and what to do in each branch. There is no ambiguity left about calling it or acting on its results.

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?

Schema coverage is 100% and already documents 'query' as name, part of a name, or city, so the baseline is 3. The description adds real meaning beyond the schema: typos are tolerated, and an empty query lists all clients rather than returning nothing, which changes how an agent should call it for discovery.

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 verb and resource ('Find clients of the connected facturo account') plus the searchable fields (name or city), fuzzy tolerance, and the empty-query edge case. That is enough for an agent to distinguish it from get_client (single lookup) or create_client without opening 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 explicit when-to-use guidance and a downstream workflow: call it before previewing for a client that may exist, then pass client_id to preview_invoice. It also spells out how to act on each 'match' outcome, including the ambiguity case ('several: ask the user which one').

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