Skip to main content
Glama

Get a company's roles

company_roles
Read-onlyIdempotent

One company's open tech roles on Techny and its profile: sector, headquarters, stage and funding rounds with their sources. All in one card, roles included. Says so when it has no open roles.

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_roles"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesThe company's name or id, for example "Tabby" or "tabby"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds real behavior beyond them: the response bundles roles with profile data and sources, and it explicitly discloses the empty case ('Says so when it has no open roles'), which is exactly the kind of edge-case behavior an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key content is front-loaded, but the middle sentence ('All in one card, roles included') restates what the first sentence already said and 'card' is unexplained jargon. The fragments read like terse notes rather than clean prose, costing clarity.

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?

With no output schema, the description carries the burden of describing return values, and it does so reasonably: profile fields, sourcing of funding rounds, inclusion of roles, and the empty-result message. Minor gaps remain around the ambiguous 'card' structure and the exact shape of the returned roles.

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, including a worked example ('Tabby' or 'tabby'), so the schema already does the work. The description adds no further meaning about accepted name/id forms, so the baseline of 3 applies.

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 states a specific resource (one company's open tech roles plus its profile) and enumerates the profile contents: sector, headquarters, stage, funding rounds with sources. It is clearly a single-company lookup rather than a role-level lookup, so an agent can distinguish it from get_role and search_roles without opening the schema, though no sibling is named explicitly.

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?

Usage is only implied by the scope phrase 'One company's open tech roles' – the agent must infer that this is the tool for company-level lookups versus a specific role or a broad search. There is no explicit when-to-use, when-not-to-use, or named alternative such as search_roles.

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