datacrazy_instances_get
Read-onlyIdempotent
Buscar instancia por ID (GET /api/v1/instances/{id}).
Bulk support: accepts ids for batched execution.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| ids | No | ||
| query | No | ||
| account | No |
DataCrazy
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.8/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover readOnly and idempotent nature. The description adds context about bulk support, which is a behavioral aspect not fully captured by annotations. No contradictions.
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 extremely concise, consisting of two short sentences with no extraneous information. It follows a clear format of stating purpose then a note on bulk support.
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?
While the purpose is clear, the description omits details about response content, prerequisites, or how it fits with sibling tools. It is adequate but not fully complete for comprehensive understanding.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description explains 'id' and 'ids' implicitly via bulk support, but does not clarify the 'query' or 'account' parameters. With 50% coverage, it fails to fully explain the input schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves an instance by ID, with Spanish verb 'Buscar' and resource 'instancia'. It also mentions bulk support, distinguishing it from list operations.
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 mentions bulk support but does not explicitly contrast with the sibling list tool or specify when to use this versus other retrieval methods. The usage context is implied but not fully articulated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.2/5.0
Disambiguation5/5
Every tool maps to a distinct resource-action pair (e.g., leads_create vs businesses_create). Even nested tools like leads_activities_list are clearly scoped from general activities_list. No two tools appear to do the same thing.
Naming Consistency5/5
All resource tools follow the exact pattern 'datacrazy_<resource>_<action>' with actions being create, get, list, patch, update, delete, plus a few composite verbs like finish_create or actions_win_create. The naming is uniform and predictable.
Tool Count2/5
70 tools is far beyond the usual 3-15 range for an MCP server, making it overwhelming and unwieldy for agents. Although the scope is broad (full CRM), the sheer count exceeds the recommended threshold for effective tool discovery.
Completeness4/5
Most resources have full CRUD coverage (leads, activities, tags, lists, products, businesses, business_loss_reasons). Some gaps exist: attendants only have get/list, conversations lack delete/update, and pipelines are read-only. These are minor and workable, but not complete lifetime coverage.