Skip to main content
Glama
Sign In
Pubrio

Pubrio

Official
by pubrio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lookup_company

Retrieve comprehensive company data using a domain, LinkedIn URL, or Pubrio domain search ID.

Instructions

Look up detailed company information by domain, LinkedIn URL, or domain search ID

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": "lookup_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoCompany domain (e.g. "google.com")
linkedin_urlNoCompany LinkedIn URL
domain_search_idNoPubrio domain search ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

C2.9/5.0
Behavior2/5

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

Given no annotations, the description carries the full burden of behavioral disclosure. It only states 'Look up detailed company information' without revealing mutation status, rate limits, authorization requirements, or the scope of 'detailed'. This is insufficient for safe invocation.

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?

Single sentence with no wasted words. Front-loaded with verb and resource. Efficiently conveys the essential input variety.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and many sibling tools (enrich_company, lookup_company_linkedin, search_companies), the description is too sparse. It does not explain return structure, depth of information, or how it differs from near-identical tools. Incomplete for effective decision-making.

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 each parameter already has a description. The tool description adds no extra meaning beyond listing the parameters. It does not clarify whether parameters are mutually exclusive, optional combinations, or preferred input format.

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?

The description clearly states the action (look up) and resource (detailed company information), and lists the three possible input identifiers. This distinguishes it from search-based siblings, but does not explicitly differentiate from enrich_company or find_similar_companies.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as enrich_company, lookup_company_linkedin, or search_companies. The description assumes the agent knows the purpose without contextualizing its role among siblings.

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