Skip to main content
Glama
ariregister-mcp

ariregister-mcp

by aanndryyyy

Get representation rights

get_representation_rights
Read-only

Search by a representative's name or registry code to retrieve the companies they may represent, their roles, sole or joint representation rights, conditions, and joint-representation groups.

Instructions

Who may represent companies, and how (REST, needs an API key): persons with their role and whether they can act alone (exclusiveRightOfRepresentation), plus special conditions and joint-representation groups. Search by the REPRESENTATIVE: a person's identification code, or a company's registry code with person_type J when the representative is itself a company, or by name. For who can represent a given company, use get_company with include ['related_persons'] instead.

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_representation_rights"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1).
birthdayNo
languageNoLanguage of classifier texts (statuses, roles, legal forms): 'eng' (default) or 'est'.
page_sizeNoResults per page, 1–1000 (default 100).
first_nameNo
entity_codeNoPersonal identification code or company registry code.
person_typeNoP = natural person (default), J = legal person.
entity_code_countryNoISO 3166-1 alpha-3 country code, e.g. 'EST', 'FIN', 'LVA'.
surname_or_company_nameNo

Output Schema

NameRequiredDescriptionDefault
listYes
totalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds the key operational detail that this is a REST endpoint requiring an API key — a real constraint an agent must satisfy before calling. It also discloses that results carry joint-representation groupings and conditional rights, which hints at non-flat result structure. It stops short of describing rate limits or pagination behavior, so it is strong but not exhaustive.

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 dense but well-ordered sentences: the what-and-returns first, the search-key mechanics second, the alternative last. The parenthetical 'REST, needs an API key' is slightly awkwardly placed mid-sentence and the role-parenthetical is heavy, but there is no filler or repetition.

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?

With an output schema present and read-only/open-world annotations, the description does not need to enumerate return fields, and it correctly focuses on access method, search semantics and alternative routing. For a 9-parameter optional-filter tool the coverage is nearly complete; only pagination behavior and the meaning of `language` relative to returned role texts are unaddressed.

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?

Schema coverage is 67%, and the description adds genuine meaning beyond it by explaining the `entity_code` / `person_type` interaction (registry code only meaningful with person_type J) and by framing the name-based path. The paging, language, birthday and country-code parameters are left entirely to the schema, which is acceptable at this coverage level but leaves some semantics unadded.

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 states a specific resource and question it answers — 'Who may represent companies, and how' — and immediately names the exact shape of the payload: persons, their role, whether they can act alone (`exclusiveRightOfRepresentation`), special conditions and joint-representation groups. It also distinguishes itself from the sibling route `get_company` with `include: ['related_persons']`, so an agent can choose between the two without opening either schema.

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?

It gives explicit routing: search by the REPRESENTATIVE using a person's identification code, a company registry code with `person_type` J, or a name — and states the inverse case ('For who can represent a given company, use get_company with include [related_persons] instead'). Both the when-to-use and the when-to-use-something-else conditions are spelled out rather than inferred.

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