How It Works
how_it_worksExplain what Barnir Hired does, when to use it, its privacy stance, and where to run a full analysis.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
barnir-hired
TDQS
A3.9/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It clearly indicates the tool is informational ('Explain...') and specifies the content areas it will cover. No side effects or hidden behaviors are evident, and the verb itself signals a read-only explanatory action.
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 primary action and then lists the key topics efficiently. Every word contributes to conveying the tool's purpose with no repetition or filler.
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 zero-parameter informational tool with no output schema, the description covers the essential dimensions: what the tool does, when to use the product, privacy stance, and where to run analysis. It is adequate, though it could briefly mention how this tool relates to the sibling tools for fuller orientation.
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 has zero parameters, so the description is not expected to elaborate on parameter meaning. The baseline of 4 applies since no parameter documentation is needed and the description's content is entirely independent of inputs.
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 uses a specific verb ('Explain') and a clear resource ('what Barnir Hired does') with additional covered topics. It is distinct from the sibling tools in subject matter, though it does not explicitly name or differentiate itself from get_role_guidance or list_roles.
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?
The description implies usage: an agent would call this tool when it needs a general explanation of Barnir Hired, its use cases, privacy stance, and analysis workflow. However, it provides no explicit when-to-use versus alternatives or exclusion guidance, leaving the selection to inference.
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.