Lim

query_limnowcoinlink

Read-only

Find LimNowCoinLink 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_limnowcoinlink"
  }
}

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 1, 2026

TDQS

A3.5/5.0

Behavior2/5

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

readOnlyHint=true already establishes this is a safe read, and the schema descriptions already explain 'fetch one by id; omit to query many.' The description restates that same id/query split without adding anything new about precedence, result ordering, or projection behavior.

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?

A single front-loaded sentence with the resource and both usage modes; nothing extraneous.

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?

For a 6-parameter read tool with a nested MongoDB-style filter and no output schema, the definition is minimally adequate. It says nothing about how query interacts with id, how pagination/sort behave, or what the response looks like, leaving the schema to carry that load.

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 83%, so the schema already documents id, skip, sort, limit (with clamping), query (MongoDB-style with example), and fields. The description mentions only id and query and adds no syntax or semantics beyond the schema; 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 (Find) and resource (LimNowCoinLink records), and splits the two operating modes (single record by id vs. filtered list via query). It clearly distinguishes itself from siblings by entity name, though it offers no explicit contrast with the many other query_lim* tools.

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?

The clause 'pass id for one record, or query for a filtered list' tells the agent which parameter selects which mode, which is real routing guidance. It stops short of stating whether id and query can be combined or which takes precedence.

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?