Paidnice

List inbound SMS

list_inbound_sms

Read-onlyIdempotent

Returns SMS messages the organisation received through Paidnice, most recent first, up to 100 per page. Each message shows the sender, the matched contact when known, and the text. 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_inbound_sms"
  }
}

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.
`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

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the closing 'Read only.' adds nothing new and is largely redundant. What the description does contribute beyond annotations is ordering (most recent first), the 100-per-page cap, and the fields returned per message, which is modest but genuine added context.

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 plus a short safety tag; the core behavior (what, ordering, page size, per-item fields) is front-loaded with no filler or repetition beyond the redundant 'Read only.' remark.

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 simple paginated read with a fully documented schema, complete annotations, and an output schema, the description covers what the tool returns and how paging behaves. The only shortfall is not routing the agent between this and list_inbound_email.

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 limit, cursor, and organisationId are already fully documented, including the cursor's nextCursor origin and the 100 maximum. The description's 'up to 100 per page' restates the schema's maximum rather than adding format or usage nuance, so baseline 3 applies.

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 ('Returns SMS messages the organisation received through Paidnice') plus ordering and page size. The SMS-vs-email distinction from the sibling list_inbound_email is left implicit, so it is clear on its own but doesn't actively differentiate from the nearest sibling.

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?

Usage is implied by the description (retrieve received SMS for an organisation, paginate with cursor), but there is no explicit when-to-use/when-not guidance and no mention of the closely named list_inbound_email sibling, leaving the agent to infer the split.

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?