Skip to main content
Glama
compiuta-origin

Connhex MCP Server

Official
by compiuta-origin
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Get Service Schema

get_schema
Read-only

Fetches the schema of all resource types, including attributes and relationships, to guide API requests for creating, updating, filtering, and including related records.

Instructions

Schema of every resource type exposed by this Connhex JSON:API service for the current deployment.

Shape:

  • Top-level keys are resource type names. Use them as the resource_type argument to the corresponding *_resource tools.

  • Each value is a dict of fields:

    • Entries with a type key are attributes (e.g. String, Date, Object). isArray: true indicates a list-valued attribute.

    • Entries with a link key are relationships. The link value is the related resource type — pass it (or a comma-separated list) as the include argument to fetch related records inline. isArray: true means a to-many relationship; inverse is the field name on the other side.

Internal/system fields present on every type:

  • tenants, createdAt, updatedAt are managed by the platform. Do NOT include them in create/update payloads and do not surface them as user-facing data unless explicitly asked.

Read this resource before constructing filters, includes, or create/update payloads — it is the source of truth for valid types and field names.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

Annotations already declare the tool is read-only and not destructive. The description adds valuable context: the shape of the response, listing internal fields (`tenants`, `createdAt`, `updatedAt`) and explicitly stating they should not be included in payloads. This goes beyond what annotations provide.

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

Conciseness4/5

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

The description is well-structured with paragraphs and bullet points for shape. It is front-loaded with the purpose. While slightly verbose, every sentence adds value. Minor improvement could be trimming redundancy.

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

Completeness5/5

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

Given the presence of an output schema (context signals: 'Has output schema: true'), the description does not need to detail return values. However, it still provides a thorough explanation of the schema structure and usage notes, making it complete for an agent.

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

Parameters4/5

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

There are no parameters; schema description coverage is 100%. The description adds meaning by explaining the output structure and how to interpret fields (attributes vs relationships). The baseline for zero params is 4, and the description exceeds it.

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 explicitly states the tool provides the schema of every resource type exposed by the Connhex JSON:API service. It uses specific verbs ('Get Service Schema') and clearly distinguishes itself from sibling tools by being the source of truth for types and field names.

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

Usage Guidelines5/5

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

The description explicitly advises agents to 'Read this resource before constructing filters, includes, or create/update payloads.' It also explains how to use the output with other tools (e.g., `resource_type` argument). No alternatives needed as this tool is unique.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/compiuta-origin/connhex-tools'

If you have feedback or need assistance with the MCP directory API, please join our Discord server