Skip to main content
Glama
Sign In
EspoCRM Assistant

EspoCRM Assistant

by The-Keep-Studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

crm_metadata

Read the allowlisted field metadata for any entity in EspoCRM, returning the schema of fields to guide data access.

Instructions

Read allowlisted field metadata for one entity.

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>"
    },
    "name": "crm_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
entityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations provided; description says 'Read' suggesting read-only but does not confirm idempotency, auth requirements, or error handling. Minimal behavioral disclosure given a simple read operation.

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?

Single sentence, front-loaded, no unnecessary words. Every word earns its place.

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

Completeness2/5

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

Low complexity tool but no output schema and description does not explain what 'field metadata' includes or return format. Lacks completeness for a metadata retrieval tool.

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?

Single parameter 'entity' lacks schema description (0% coverage) and the description only says 'one entity' without specifying whether it is a name, ID, or valid values. Does not compensate for missing schema info.

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?

Description clearly states verb 'Read', resource 'field metadata', and specificity 'allowlisted' and 'for one entity'. Differentiates from sibling tools which handle records, duplicates, or exports.

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?

Description implies usage for retrieving metadata about a single entity, but does not explicitly state when to use this over siblings like crm_get or crm_search. Context from sibling names partially fills the gap.

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