Skip to main content
Glama

run_pa_companies_search

Search Panama's Registro Público for suspended, dissolved, merged, or closed companies by name or folio, returning status, register type, and key dates.

Instructions

Search the Panama Registro Público (Consulta de Folios Suspendidos) by company name or folio number: name, folio, status, register type, incorporation date and status date. Covers suspended, dissolved, merged and closed entities. 1 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": {
      "keyword": "<keyword>"
    },
    "name": "run_pa_companies_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoStatus. Options: active = Active, inactive = Inactive / dissolved
keywordYesCompany name or folio. e.g. copa
max_itemsNoMax items (up to 250)
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the returned fields, that suspended/dissolved/merged/closed entities are covered, and a cost model ('1 point per returned record'). It omits auth requirements, rate limits, and pagination behavior, leaving meaningful gaps for a no-annotation tool.

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 compact sentences, front-loaded with the action and registry, then the coverage and cost. Every clause carries information; no 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?

For a search tool with no output schema, the description tells the agent what fields come back and what entity states are included, and even the credit cost. Missing only paging semantics and usage alternates, which are minor given the complete input 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 the schema already documents keyword, status enum, max_items and start_page. The description only maps the keyword to 'company name or folio number', adding little beyond the schema. Baseline 3 is appropriate.

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

Purpose4/5

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

States a specific verb ('Search') and resource (Panama Registro Público / Consulta de Folios Suspendidos), and enumerates the returned fields plus entity coverage. It does not explicitly differentiate itself from the run_pa_companies sibling, so it stops short of a 5.

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 phrase 'by company name or folio number' implies how to use the keyword input and mentions which entity states are covered, but there is no explicit when-to-use vs. when-not, and no mention of the run_pa_companies alternative tool.

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