Lim

query_limmodulepref

Read-only

Find LimModulePref 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_limmodulepref"
  }
}

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.

AddedOct 28, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the id-vs-query dispatch behavior, but says nothing about default result volume, clamping, or sort/filter interactions — details that live only in the schema and are not surfaced here.

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, front-loaded with the verb and resource, with the branching rule in the same breath. No filler, though the dash construction is slightly terse for an agent parsing two distinct modes.

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 read-only query tool with no output schema, the description covers the essential invocation modes. It is silent on return shape, pagination defaults, and the interaction of id with query/limit/sort, leaving real ambiguity for a 6-parameter nested-object 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 coverage is 83%, so the schema already documents id, skip, sort, limit, and query. The description reinforces the id/query distinction but adds no new semantics, and the undocumented 'fields' parameter gets no explanation anywhere.

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 ('LimModulePref records') and splits the two access modes: single record via id, filtered list via query. It does not explain what a LimModulePref is or differentiate from the ~80 sibling query_lim* tools, but the resource name itself does the sibling disambiguation.

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?

The description implies usage by mapping id -> one record and query -> filtered list, which is a genuine mode-selection rule. It offers no when-not-to-use guidance, no mention of what happens when both id and query are supplied, and no pointer to alternative tools.

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?