Skip to main content
Glama

Portugal company

run_pt_companies
Read-onlyIdempotent

Get one company from the Portugal registry (Registo Comercial publications portal) by NIF/NIPC or registry link: name, legal form, registered seat (street, postal code, locality, parish, municipality, district), number of publications and the newest publication. 15 points 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_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesNIF/NIPC or registry URL. e.g. 500697256

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, openWorld, non-destructive), and the description adds genuinely new behavioral context: the upstream source is the Registo Comercial publications portal and each returned record costs 15 points. It does not state what happens when the NIF is not found or invalid, which would round out the behavior.

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?

Two sentences, both earning their place: identity/source and inputs first, field payload second, cost last. No filler or repetition of the title.

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 correctly compensates by enumerating the returned fields (name, legal form, seat breakdown, publication counts, newest publication) and discloses the per-record point cost. The main remaining gap is failure behavior for unknown or malformed identifiers.

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 parameter is documented with a worked example (500697256). The description restates that the value may be a NIF/NIPC or a registry URL, which the schema already conveys, so it adds no format or validation detail beyond structured data. 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 and resource ('Get one company from the Portugal registry') and names the exact source portal (Registo Comercial publications portal). It further enumerates the returned fields, so an agent can distinguish this single-record lookup from the sibling list/search tool run_pt_companies_search 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 Guidelines4/5

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

The description gives clear selection context: use this when you already hold a NIF/NIPC or a registry link for one specific company. It does not explicitly say 'use run_pt_companies_search instead if you only have a name', so the routing to the sibling is left implicit rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources