Skip to main content
Glama
Sign In
EspoCRM Assistant

EspoCRM Assistant

by The-Keep-Studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

crm_get

Read one CRM record by providing entity type and record ID. Optionally select specific fields to retrieve.

Instructions

Read one allowlisted CRM record.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entity": "<entity>",
      "record_id": "<record_id>"
    },
    "name": "crm_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
entityYes
record_idYes
fieldsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

The description indicates a read operation ('Read'), implying no side effects, but no annotations exist. It does not disclose authentication needs, rate limits, or what 'allowlisted' means in practice. Minimal behavioral context is provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but under-specified. It lacks structure and does not earn its place by providing sufficient detail for an agent to correctly invoke the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (3 parameters, no output schema, 0% schema coverage), the description is severely incomplete. It does not explain the allowed entities, record ID format, fields parameter, or return behavior. An agent would lack critical information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage and no explanation of the three parameters (entity, record_id, fields), the description fails to add meaning beyond the schema. It does not clarify allowed entities, record ID format, or fields usage.

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 clearly states the action ('Read') and resource ('CRM record'), and the qualifier 'allowlisted' suggests a restriction. It distinguishes from sibling tools like crm_search which retrieves multiple records. However, 'allowlisted' is ambiguous without further explanation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like crm_search for multiple records or crm_metadata for schema information. The description does not mention prerequisites or exclusion criteria.

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

Deploy Server

Other Tools