Skip to main content
Glama
Sign In

Sk Rpo

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Rpo Entity Detail

rpo_entity_detail
Read-onlyIdempotent

Fetch the full RPO record for one entity: legal forms, registered address history, statutory bodies (directors/executives), stakeholders (owners/partners), equity and shares, predecessors (mergers/splits), statistical classification codes, and the source register (Obchodný register / Živnostenský register / etc.) with registration number. Pass either id (the internal RPO id returned by rpo_search_entity) or ico (the 8-digit IČO) — if you pass ico, this tool resolves it to the internal id first via an exact-identifier search.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
idNoInternal RPO entity id, from rpo_search_entity results (the `id` field).
icoNoIČO — the 8-digit Slovak business identifier, e.g. "31333532". Used to look up the entity if `id` is not given.
includeHistoryNoInclude historical (superseded) names, addresses, legal forms etc., not just the current ones. Default true.
includeOrganizationUnitsNoInclude organizational units (branches) of the entity. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds genuine behavior beyond them: passing `ico` triggers a prior exact-identifier resolution step to an internal id, which changes the call's cost and failure modes. It does not cover not-found behavior or payload size.

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 sentences, front-loaded with purpose, then the identifier-selection rule. The content enumeration is long but earns its place because there is no output schema, so it is the only description of return contents.

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 no output schema, the description carries the burden of describing returned data and does so thoroughly, including source register types and IČO resolution. Minor gaps remain around failure modes and whether history/organization-unit defaults are already reflected in the response size.

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 100%, so the baseline is 3. The description still adds value by characterizing the `ico` path as an 'exact-identifier search' resolution — meaning no fuzzy matching — and by framing `id` as authoritative when both are supplied, which the schema only hints at.

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?

Opens with a specific verb+resource ('Fetch the full RPO record for one entity') and enumerates exactly what that record contains (legal forms, address history, statutory bodies, stakeholders, equity, predecessors, classification codes, source register). This clearly separates it from the sibling rpo_search_entity, which returns the id this tool consumes.

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?

Explicitly tells the agent that `id` comes from rpo_search_entity results and that `ico` is an acceptable alternative, so the search-then-detail workflow is implied without ambiguity. It stops short of stating exclusions or expected failure cases (e.g. what happens if the IČO matches nothing).

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

All Sk Rpo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources