Skip to main content
Glama
Sign In
@vitrion/zentria-mcp

@vitrion/zentria-mcp

Official
by vitrionbv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-organization

Read-only

Retrieve a sales organization's details by its ID. Use this to access specific organization information from Zentria CRM when you need accurate sales:read data.

Instructions

Fetch a sales organization (GET /api/public/sales/organizations/{id}). Scope: sales:read.

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": {
      "id": "<id>"
    },
    "name": "get-organization"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOrganization id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark readOnlyHint=true, and the description adds the HTTP method GET and the required auth scope 'sales:read'. This gives useful operational context beyond the annotation without contradicting it.

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?

One compact sentence states the action, resource, endpoint, and auth scope with no filler. Every element earns its place.

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

Completeness4/5

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

For a simple read-only fetch with one fully documented parameter and a clear endpoint, the definition is sufficient for correct selection and invocation. It does not describe the response shape, but no output schema exists and 'Fetch' implies the organization is returned.

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 coverage is 100% and the single 'id' parameter is already described as 'Organization id.' The description adds no extra parameter detail, so baseline 3 is appropriate.

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 names the exact verb ('Fetch'), resource ('sales organization'), and HTTP endpoint including {id}. This clearly distinguishes it from list-organizations and other get-* siblings.

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?

The singular resource and path parameter make the use case clear: retrieve one organization by id. It does not explicitly mention list-organizations as the alternative, but the context is unambiguous enough.

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