Skip to main content
Glama

Zoeb Nomi

Map a job description to public work

fit_to_role
Read-onlyIdempotent

Map a job description to Zoeb Nomi's public work (zoebnomi.com) with quoted evidence, and list requirements with no public evidence as gaps. Never answers compensation, availability, location or work authorization.

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": {
      "job_description": "<job_description>"
    },
    "name": "fit_to_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_descriptionYesThe job description text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. Beyond that, the description adds real behavioral context: results must be backed by quoted evidence, and unmatched requirements are surfaced as gaps rather than inferred. It stays silent on how much of a JD is processed at once, but that is a minor omission given the annotation coverage.

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?

Two tightly written sentences with no filler. The core action and its evidence standard come first, with the scope exclusions placed last, so the most important information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, annotation-covered tool with no output schema, the description supplies everything an agent needs: the input type (a job description), the output convention (quoted evidence plus a gaps list), and the topics it will refuse. Nothing material is left out.

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?

With one parameter and 100% schema description coverage, the schema already documents job_description including its length bounds. The description adds no format or syntax guidance about the input, so the baseline 3 applies.

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 gives a specific verb and resource: 'Map a job description to Zoeb Nomi's public work (zoebnomi.com)'. It also states the output shape ('with quoted evidence' and 'list requirements with no public evidence as gaps'), which no sibling (check_citations, verify_claim) shares, so an agent can tell them apart without opening a 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?

It clearly defines the context in which to use this tool (matching a JD against public work) and gives explicit exclusions: compensation, availability, location and work authorization are never answered. It does not name an alternative tool for those excluded topics, which keeps it below a 5, but the boundary is stated unambiguously.

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.