Skip to main content
Glama

run_pt_company_filings

List Portuguese company publications from the Registo Comercial portal by NIF/NIPC or registry link, showing date, act type, municipality, and attachment presence, newest first.

Instructions

List the publications of a Portugal company (Registo Comercial publications portal) by NIF/NIPC or registry link, newest first: date, act type (registry acts, accounts deposits, notices, convocations), municipality and whether a text / attachment exists. 2 point per returned record.

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": {
      "company": "<company>"
    },
    "name": "run_pt_company_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesNIF/NIPC or registry URL. e.g. 500697256
max_itemsNoMax items (up to 250)
start_pageNoStarting page (80 publications per page)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does deliver: it discloses sort order (newest first), enumerates the returned fields (date, act type, municipality, text/attachment presence), and even states a cost ('2 point per returned record'). It omits pagination/rate-limit behavior beyond the schema, but the operational context is far richer than a bare listing statement.

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?

Front-loaded with the core purpose, then a compact enumeration of return fields and the per-record cost. The colon-heavy single sentence is dense but every clause (fields, ordering, act types, cost) adds information; nothing appears to be filler.

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?

There is no output schema, so the description usefully compensates by listing the fields a result contains and the ordering. For a read-only, three-parameter listing tool this is largely complete; only pagination mechanics and result volume limits are left to the schema.

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 description coverage is 100%, so all three parameters are already documented in the schema. The description restates the 'company' input ('by NIF/NIPC or registry link') but adds no format or constraint detail for max_items or start_page beyond what the schema already provides, so the baseline 3 applies.

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?

States a specific verb ('List') and resource ('publications of a Portugal company'), scoped to the Registo Comercial portal. It is clearly distinguishable from sibling company tools like run_pt_companies and run_pt_companies_search, which return company data rather than publication records.

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

Usage Guidelines3/5

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

The description identifies the accepted lookup keys ('by NIF/NIPC or registry link') and the source portal, which implies usage, but it never states when to prefer this tool over alternatives such as run_pt_companies_search or how to obtain the identifier first. Usage is inferable but not explicitly guided.

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