Skip to main content
Glama

Resolve Company

resolve_company
Read-onlyIdempotent

[Read · free] Look up a company saved in Flux by exactly one of name (case-insensitive exact match), linkedin_url, linkedin_company_id (LinkedIn's numeric id) or company_id, free. Returns company_id, linkedin_company_id, name, linkedin_url, page_type and coverage for you: connected_people_current (people connected to you, meaning they engaged with posts you can see, are in your campaigns or segments, or you pulled or enriched them, who hold a current position there) and engagers_current (those of them who engaged with your posts, with their engagement total). A name shared by several saved companies returns candidates to pick from. A company that is not saved returns _meta.next_step = linkedin_company_info (1 credit), which saves it. Generic placeholders (Self-employed, Freelance, Stealth...) are refused. Pure DB read, no LinkedIn pull, 0 credits.

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

Input Schema

NameRequiredDescriptionDefault
nameNoCompany name, exact and case-insensitive
company_idNocompanies.id UUID
linkedin_urlNoCompany LinkedIn URL (linkedin.com/company/…)
linkedin_company_idNoLinkedIn's numeric company id, as linkedin_company_info returns it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/closed-world, and the description adds substantial context beyond them: pure DB read, no LinkedIn pull, 0 credits, refusal of generic placeholders (Self-employed, Freelance, Stealth...), and candidate list on ambiguous names. These are real edge-case behaviors an agent cannot infer from the annotations.

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-loads cost and read-only status in a bracketed tag, then constraints, then return shape — good ordering with no filler sentences. The single dense paragraph is long and the coverage-field enumeration is heavy, but with no output schema that detail is load-bearing rather than padding.

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

Completeness5/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 return contract and does so: company_id, linkedin_company_id, name, linkedin_url, page_type, plus the connected_people_current and engagers_current coverage fields and their definitions. It also documents the two non-happy paths (candidates, _meta.next_step) and the placeholder refusal, leaving little an agent needs unknown.

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, but the description adds meaning the schema does not enforce: the one-of constraint across the four identifiers, case-insensitive exact matching for name, and that linkedin_company_id is LinkedIn's numeric id as returned by linkedin_company_info. It stops short of explaining precedence or error text when multiple identifiers are supplied.

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 ('Look up a company saved in Flux') and enumerates the exact identifier keys accepted. It implicitly distinguishes itself from the sibling linkedin_company_info by noting this is a saved-record lookup with no LinkedIn pull, so an agent can route correctly without opening a schema.

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

Usage Guidelines5/5

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

Explicitly constrains input to 'exactly one of' four identifiers and names the alternative path when the company isn't saved (_meta.next_step = linkedin_company_info, 1 credit, which saves it). The free-vs-credit contrast with that alternative gives a clear selection rule.

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