Lim

query_limpaymentshield

Read-only

Find LimPaymentShield records - pass id for one record, or query for a filtered list.

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": "query_limpaymentshield"
  }
}

Input Schema

Name	Required	Description
`id`	No	Fetch one record by id; omit to query many
`skip`	No	Records to skip before the first result; 0 or more.
`sort`	No	Sort field; '-' prefix for descending
`limit`	No	1-500; defaults to 50. Out-of-range values are clamped.
`query`	No	MongoDB-style filter, e.g. {"status": "active"}
`fields`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true, so safety is already covered. The description adds the single-vs-many mode distinction, but says nothing about pagination defaults, maximum result sizes, whether query is required for list mode, or what the response contains. With annotations carrying the safety profile, this is adequate but thin.

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?

A single sentence that front-loads the verb and resource and then gives the mode switch compactly. No wasted words, though the construction is slightly dense.

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?

No output schema exists, so the description must carry the calling contract, and it does cover access patterns and the two modes. It is a bit incomplete regarding default limits (only in schema) and response shape, but overall sufficient for a read-only query tool with well-described parameters.

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 83%, so most parameter meaning is already in the schema. The description reinforces the id/query split, which helps, but adds no new detail on sort syntax, fields projection, or the nested MongoDB-style query beyond what the schema states.

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: find LimPaymentShield records, with two modes (id for one record, query for a filtered list). The purpose is clear, though 'LimPaymentShield' is a domain-specific name that carries little meaning on its own apart from the many sibling query_lim* tools that follow the same pattern.

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 describes the two invocation modes and how to select between them: pass id for one record, or query for a filtered list. It does not cover when to prefer this over sibling tools (e.g., the pay-related query_limpay* tools), but the id/query split is the primary decision an agent must make.

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

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