Skip to main content
Glama
Sign In

Lim

by app.base44.lim
OverviewDiscussionsAdmin

query_limtoolrequest

Read-only

Find LimToolRequest 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_limtoolrequest"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoFetch one record by id; omit to query many
skipNoRecords to skip before the first result; 0 or more.
sortNoSort field; '-' prefix for descending
limitNo1-500; defaults to 50. Out-of-range values are clamped.
queryNoMongoDB-style filter, e.g. {"status": "active"}
fieldsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes that this is a safe read operation, and the description is consistent with it. The description adds the dual lookup/list behavior but no further operational context such as permissions, result envelope, or empty-result 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?

The single sentence is front-loaded, easy to scan, and contains no filler. Its two clauses efficiently communicate both the resource and the two calling 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?

Together with the read-only annotation and detailed schema, the description is adequate for basic invocation, including lookup, filtering, pagination, sorting, and limits. However, there is no output schema, and the definition supplies no result-shape guidance, valid resource-specific filter or sort fields, or semantics for fields, leaving clear gaps for a six-parameter nested-query 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 83%, and the schema already documents id, skip, sort, limit, and query, including limit clamping and MongoDB-style filtering. The description mostly repeats the id/query distinction and does not explain the undocumented fields array or add resource-specific filter guidance.

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?

The description gives a clear verb and resource with 'Find LimToolRequest records' and explains the single-record versus filtered-list modes. It distinguishes the resource by name, but offers no LimToolRequest-specific scope or explicit differentiation from the many similarly structured sibling query 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?

It directly tells the agent to pass id for one record or use query for a filtered list, providing actionable mode-selection guidance. It does not address whether id and query can be combined, when an unfiltered list is appropriate, or any alternatives or exclusions.

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

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