Paidnice

Get contact

get_contact

Read-onlyIdempotent

Returns one contact by its Paidnice id: name, account number, status, group, SMS opt out and its contact persons (name, email, phone numbers, primary flag and whether they get reminders). Use list_contacts to find the id. Read only.

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

Input Schema

Name	Required	Description	Default
`id`	Yes
`organisationId`	Yes	Id of the organisation to act on, from list_organisations

Output Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`status`	Yes
`groupId`	Yes
`groupTitle`	Yes
`smsOptedOut`	Yes
`accountNumber`	No
`contactPersons`	Yes
`accountingSystemId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so "Read only" merely restates them. The enumeration of returned fields adds scope context, but with an output schema present it duplicates structured data rather than disclosing new behavior such as not-found handling or error responses.

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 tight sentences: the first front-loads what is returned, the second gives the lookup path and safety profile. No redundant or filler wording.

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?

For a two-parameter read tool with full annotations and an output schema, the description covers purpose, identifier source, and safety. Only minor gaps remain, such as what happens when the id is not found or does not belong to the organisation.

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 coverage is 50%: organisationId is documented in the schema, while id has only an example. The description partially compensates by identifying id as a "Paidnice id" retrievable via list_contacts, but adds no format, range, or scoping detail for organisationId.

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 ("Returns one contact by its Paidnice id") and enumerates the returned facets, including nested contact persons. The trailing instruction to use list_contacts clearly separates it from the list variant, so an agent can distinguish it from list_contacts and check_contact_policies without opening schemas.

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?

Explicitly routes the agent: "Use list_contacts to find the id", naming the sibling that supplies the required identifier. It gives clear context for use but stops short of stating when-not-to-use conditions (e.g. fetching many contacts at once) beyond that single routing hint.

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

All Paidnice 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?