List Roles
list_rolesList the technical go-to-market roles Barnir Hired covers, with what each role is and what hiring managers actually screen for.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
barnir-hired
TDQS
A4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It communicates that the tool returns a list of roles with explanatory and screening-related content, and the verb 'List' implies a non-mutating operation. However, it does not explicitly state whether any permissions are needed or if the response is a formatted summary, though these are minor for a simple listing tool.
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?
The description is a single, focused sentence that front-loads the action ('List') and then defines the scope and content. Every phrase adds value—there is no fluff or repetition of the tool name.
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?
For a simple zero-parameter tool with no output schema, the description explains what the result will include. It does not specify the exact return structure or any limitations (e.g., whether roles are sorted), but the low complexity makes this a minor gap, not a blocker.
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?
The tool takes zero parameters, so the input schema is already complete and no parameter-usage explanation is needed. The description adds useful context about what the returned list will contain, which is more than the empty schema provides.
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?
The description clearly states the verb 'List', the resource ('technical go-to-market roles Barnir Hired covers'), and the content of the result (role descriptions and what hiring managers screen for). This makes the tool's purpose immediately discernible and distinct from sibling tools like get_role_guidance, which implies a more targeted lookup.
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?
The description does not provide any guidance on when to use this tool versus get_role_guidance or how_it_works. No explicit context, exclusions, or alternative routing is given; the agent must infer usage from the name and description alone.
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.
TDQS
A4/5.0
Disambiguation4/5
The tools are mostly distinct: one lists all roles, one gives detailed guidance for a single role, and one explains the service itself. There is minor overlap in that list_roles also summarizes what each role is and what hiring managers screen for, but the descriptions clarify that get_role_guidance is deeper and role-specific.
Naming Consistency4/5
Two tools follow a clear verb_noun pattern (get_role_guidance, list_roles), while how_it_works is a phrase rather than a verb_object convention. However, all names are lowercase snake_case and readable, so the set is mostly consistent with one minor deviation.
Tool Count5/5
Three tools is well-scoped for a niche service focused on role guidance and product explanation. Each tool serves a clear purpose with no redundancy, and the count feels neither thin nor bloated.
Completeness4/5
The surface covers list roles, get detailed role guidance, and explain how the product works, which forms a coherent user journey. The only minor gap is that there is no in-server tool to run a full analysis, but the how_it_works description acknowledges that external flow rather than requiring this server to include it.