Skip to main content
Glama

Get roles

get_roles
Read-onlyIdempotent

Everything about up to 5 roles by id from search_roles: all skills, majors, other boards and the employer's full posting text (hiring boilerplate left out), for checking a role against a resume or answering questions about it.

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": {
      "ids": "<ids>"
    },
    "name": "get_roles"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesUp to 5 role ids from search_roles (or their applyUrls).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a hard batch ceiling of 5 roles, the inclusion of full posting text, and the specific exclusion of hiring boilerplate, which tells the agent what it will and won't see before spending a call.

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?

A single dense sentence with the resource and the id-source constraint front-loaded, and no filler. The enumerated field list plus a parenthetical caveat makes it slightly packed, but each clause carries information.

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 does the work of describing the return payload (skills, majors, other boards, cleaned posting text), which is exactly what an agent needs for a read tool of this shape. It stops short of covering edge behavior such as invalid ids or requests exceeding 5.

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% and the schema already documents 'Up to 5 role ids from search_roles (or their applyUrls)'. The description's 'up to 5 roles by id from search_roles' restates that rather than adding format, error or ordering semantics, so the baseline 3 is appropriate.

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 (get) and resource (roles) and immediately draws the boundary against the sibling: this is the by-id fetch whose ids come 'from search_roles', with the returned fields enumerated (skills, majors, other boards, full posting text). An agent can tell this apart from search_roles without opening either schema.

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

Usage Guidelines4/5

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

Gives explicit intended uses — 'checking a role against a resume or answering questions about it' — and implicitly chains it after search_roles as the id source. It does not name conditions for avoiding it (e.g. bulk browsing vs. deep fetch), so it falls short of full when/when-not guidance.

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