Skip to main content
Glama

Jobiba Hiring: Post Jobs, Screen Applicants & Source Talent

Research a company

company_insights
Read-onlyIdempotent

Company research from Jobiba data: profile, verified status, open jobs, anonymous moderated employee reviews (ratings, would-recommend), interview difficulty and published pay by role.

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

Input Schema

NameRequiredDescriptionDefault
companyYesCompany name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered elsewhere. The description adds genuine context beyond that — reviews are anonymous and moderated, pay is 'published', status is 'verified' — which tells the agent about data provenance and trust characteristics. It remains silent on behavior when a company is not found or how results are ordered/paginated.

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?

One front-loaded sentence that enumerates the payload types efficiently, with no filler or redundant restatement of the title. The parenthetical qualifiers add precision rather than noise; only minor gain would come from splitting the enumeration into a clearer structure.

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?

No output schema exists, so the description carries the burden of describing return values, and it does so by naming every category of data returned. For a single-parameter read-only lookup this is nearly complete; only error/empty-result behavior is unaddressed.

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?

There is a single required parameter with 100% schema description coverage, so the schema already establishes that a company name string is expected. The description adds nothing about name matching, ambiguity handling, or accepted formats beyond what the schema provides, making baseline 3 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?

The description names a specific resource (company research on Jobiba data) and enumerates the exact content returned: profile, verified status, open jobs, anonymous moderated employee reviews, interview difficulty, and published pay by role. This lets an agent understand the scope without opening a schema, though it never explicitly contrasts the tool with overlapping siblings such as salary_research or get_job.

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, and no prerequisites or alternatives are named. The overlap with salary_research on 'published pay by role' is left for the agent to resolve on its own.

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.