Paidnice

List contacts

list_contacts

Read-onlyIdempotent

Returns the organisation's contacts (the customers it invoices), most recently created first, up to 100 per page. Use search to find a contact by name, account number or contact person email. The returned id is what the other contact, invoice and note operations take. 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>"
    },
    "name": "list_contacts"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of records to return
`cursor`	No	Opaque cursor from a previous response's nextCursor. Omit to start from the most recent record.
`search`	No	Case insensitive partial match on the contact name, account number or a contact person's email
`organisationId`	Yes	Id of the organisation to act on, from list_organisations

Output Schema

Name	Required	Description	Default
`data`	Yes
`nextCursor`	No	Pass as the cursor query parameter to fetch the next page. Absent on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the trailing "Read only." is redundant. The description earns credit for disclosing behavior beyond annotations: result ordering (most recently created first) and a hard page cap of 100, both of which matter for how an agent paginates.

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?

Four short sentences, tightly ordered: what it returns, how to filter, what the id is for, safety. No filler, and the scope and ordering are front-loaded.

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 values need no explanation, and the description still clarifies ordering, page cap and the downstream use of the id. The only small gap is that cursor-based continuation is left entirely to the schema, which is acceptable for a simple four-parameter list tool.

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 all four parameters are already documented, which sets the baseline at 3. The description restates the search semantics and explains the significance of the returned id, but adds nothing about limit or cursor beyond what the schema already says.

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 the organisation's contacts") and goes further by defining what a contact is ("the customers it invoices"), plus ordering and page size. This is clearly distinguishable from get_contact (single record) and from the other list_* siblings.

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?

Tells the agent to use the search parameter to find a specific contact by name, account number or contact person email, and explains that the returned id feeds the other contact, invoice and note operations. It does not name sibling alternatives such as get_contact for fetching a single known contact, so routing guidance is strong but not exhaustive.

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?