Skip to main content
Glama

Get a client

get_client
Read-onlyIdempotent

One client of list_clients by id.

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": {
      "id": "<id>"
    },
    "name": "get_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id of the client

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
archivedNo
currencyNo
hourly_rateNoA decimal

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds no behavioral context of its own — nothing about not-found behavior, permissions, or the shape of the returned client, so it earns little credit beyond the annotations.

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?

It is very short and front-loaded, but the wording is a noun phrase rather than a clear statement, which costs readability. Minimal length without a complete, informative sentence leaves it under-specified rather than genuinely economical.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 values need not be described, and annotations cover the safety profile for this trivial read-by-id tool. Still, the description provides no guidance on missing-id handling or relationship to sibling get_* tools, leaving it barely adequate.

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?

There is a single parameter with 100% schema description coverage ("The id of the client"), so the schema already carries the semantics. The description only restates "by `id`" without adding format expectations, provenance of the id, or error behavior, which is the baseline for fully-covered schemas.

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

Purpose3/5

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

The phrase "One client of list_clients by `id`" does convey that this returns a single client record keyed by id, implicitly contrasting with the plural list_clients sibling. However, it is a sentence fragment with no verb, and the reader must reconstruct "get/fetch" from the tool name rather than the description.

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?

Referencing list_clients implies the use case: after listing clients, fetch one by id. There is no explicit statement of when to prefer this over list_clients or any other get_* sibling, and no note about what happens if the id is unknown.

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