Skip to main content
Glama
mcp-server-ipex

mcp-server-ipex

by Spoje-NET

Get Rights

get_rights
Read-onlyIdempotent

Lists available rights from the IPEX API so you can inspect permission and access records for B2B accounts and services.

Instructions

List of rights. IPEX API: GET /v1/rights.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_rights"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds only the underlying endpoint mapping, and says nothing about pagination, result size, or what a rights record contains — a modest but real contribution given the annotation coverage.

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?

Two short fragments, front-loaded with the resource and followed by the API mapping — no filler or repetition. It is efficient, though the terse fragment style leaves the resource under-explained.

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?

For a zero-parameter read tool with annotations covering safety, the description is nearly sufficient to call correctly. It falls short on what a "right" actually is and whether results are paginated, and there is no output schema to answer the return-shape question.

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?

The tool takes zero parameters, so the schema carries the full parameter burden and the description cannot add anything meaningful here. This lands at the baseline for a no-parameter tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List of rights" names the resource and implies a read, and the endpoint hint (GET /v1/rights) confirms retrieval. However, "rights" is ambiguous on its own (permissions? usage rights? contractual rights?) and nothing distinguishes this from siblings like get_account or get_ict_price_list, so an agent must guess at the domain object.

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?

There is no when-to-use guidance, no preconditions, and no mention of alternatives. The only routing signal an agent gets is the word "rights" plus an HTTP path, which does not say in which situations this call is appropriate.

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