Skip to main content
Glama
Sign In

Lim

by app.base44.lim
OverviewDiscussionsAdmin

query_limbucket

Read-only

Find LimBucket 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_limbucket"
  }
}

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

B3.3/5.0
Behavior2/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's burden is to add behavior beyond that and the schema. It does not: pagination defaults, clamping behavior, sort syntax, and result shape are all covered (or not) by the schema rather than the description. With annotations plus a rich schema, the description contributes almost no additional behavioral 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?

A single sentence, front-loaded with the resource and immediately followed by the two-mode split. No filler, nothing buried.

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 six optional params and no output schema, the dual-mode explanation is the essential piece and it is present. However, without an output schema the agent gets no sense of what a result looks like, and the one undocumented parameter ('fields') is not compensated for.

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 the schema already explains id, skip, sort, limit, and query; only 'fields' lacks documentation anywhere. The description's mention of id versus query restates what the schema says almost verbatim, adding no syntax or format detail.

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 pairs a specific verb ('Find') with a specific resource ('LimBucket records') and explains the two operating modes. It does not need to differentiate from siblings beyond the entity name, since the sibling set is a uniform family of per-entity query tools, but it adds no explicit contrast statement.

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?

It gives mode-selection guidance ('pass id for one record, or query for a filtered list'), which is the main decision an agent faces here. It offers no exclusions, no mention of what happens when both id and query are supplied, and no hint about when a different sibling tool would be preferred.

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