Skip to main content
Glama
Sign In

Lim

by app.base44.lim
OverviewDiscussionsAdmin

query_limcontact

Read-only

Find LimContact 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_limcontact"
  }
}

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 annotation already establishes that this is a safe read operation. The description adds useful mode behavior (one record vs list), but does not describe return shape, pagination behavior, or what happens if both id and query are supplied, so it adds only moderate context beyond annotations and schema.

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 description is a single, front-loaded sentence with no filler. It immediately conveys both modes of use.

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 six-parameter read-only query tool, the description covers the main invocation pattern but omits details such as how id interacts with query, the default/clamped limit behavior, and output expectations. Much of this is in the schema, and annotations cover safety, so it is adequate but not fully complete.

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 high (83%), so parameters like skip, sort, limit, and query are already documented in the schema. The description reinforces the id-vs-query distinction, but adds no extra syntax, constraints, or meaning beyond the schema, which is the baseline expectation.

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 specific verb ('Find') and resource ('LimContact records'), and clarifies the two operating modes: fetch by id or query a filtered list. It does not explicitly contrast with sibling tools, but since every sibling targets a different entity, differentiation is largely carried by the tool name.

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 explicitly states how to select the single-record mode ('pass id') versus the filtered-list mode ('query'). There are no exclusions or prerequisites, but the core usage distinction an agent needs is present.

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