Skip to main content
Glama

get_company_profile

Read-onlyIdempotent

Retrieve public company profile signals by company name, including headcount trends and hiring velocity, to support recruiting and market research.

Instructions

Get public company profile signals including headcount trends and hiring velocity.

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": {
      "co": "<co>"
    },
    "name": "get_company_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
coYesCompany name to analyze (e.g. 'Zoho', 'TCS')

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.8
    • addedInput schema / properties / co / description
      Added value: +"Company name to analyze (e.g. 'Zoho', 'TCS')"
  2. First observedv0.1.2

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered without description help. The description contributes that the data is 'public' and that the payload centers on headcount trends and hiring velocity, which is genuinely additive context about the tool's output domain. It says nothing about data freshness, coverage gaps, or failure behavior for unknown companies, leaving those to the output schema.

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?

One sentence, front-loaded with the operation and immediately followed by the concrete signal types. Nothing is padding and nothing important is buried.

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?

An output schema exists and the annotations carry the safety profile, so the description only needs to convey scope and content, which it largely does for a one-parameter tool. The remaining gap is sibling differentiation against search_companies and get_company_jobs, which the description never addresses.

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% with a single required 'co' parameter already documented with examples ('Zoho', 'TCS'), so the schema does the heavy lifting. The description adds nothing about name-matching behavior, ambiguity resolution, or ticker-vs-name input, which would have been the only way to exceed baseline here.

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?

Names a specific verb and resource ('Get public company profile signals') and enumerates the signal types (headcount trends, hiring velocity), which is more than a restatement of the name. It stops short of distinguishing itself from close siblings like search_companies or get_company_jobs, so an agent cannot tell from the text alone which of those to pick.

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?

There is no when-to-use or when-not-to-use guidance, no prerequisites such as 'company must exist in the index', and no mention of the sibling tools (search_companies, get_company_jobs, deep_industry_analysis) that overlap with this capability. Only the barest implied usage exists from the description's phrasing.

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