Skip to main content
Glama

searchnapply

Explain search fields

job_postings_search_fields
Read-onlyIdempotent

Purpose: Explain every search field and its values, and map job departments to their families and titles. When: Before you pick a field the user did not spell out, or when a search result is ambiguous. Cost: About 710 tokens for the field list and about 2370 for the departments breakdown.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "field": "department",
      "value": "software-it"
    },
    "name": "job_postings_search_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldNoWhich field to explain; leave it out for every field, or use department for the department map.
valueNoA department slug, only with field department, to read that department's every family and role.

Output Schema

NameRequiredDescriptionDefault
fieldsNoEvery search field with its values; present when no field argument was given, or for the field asked for.
departmentNoOne department with every family and role; present for a department value.
departmentsNoEvery department with its largest families; present for the department field.

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 readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context by disclosing the token cost of each response mode (~710 vs ~2370 tokens), which helps an agent budget context; it stops short of describing caching or exact response shape, but an output schema exists.

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?

Three labeled lines (Purpose, When, Cost) are front-loaded and free of filler. Every sentence, including the cost estimate, carries actionable information for an agent.

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 read-only, two-parameter documentation tool with an output schema and full schema coverage, the description supplies what structured fields cannot: when to invoke it and how expensive each mode is. Nothing needed to call it correctly is missing.

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 description coverage is 100% and the field enum is documented, so the schema already explains that omitting field returns everything and that department yields the map. The description reinforces this at a summary level but adds little syntax or format detail beyond the schema, 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 names a specific verb and resource: explain every search field and its values, plus map departments to families and titles. That is clearly distinguishable from search-performing siblings such as job_postings_search, since this tool only documents options rather than executing queries.

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 gives an explicit trigger: use it before picking a field the user did not spell out, or when a search result is ambiguous. It does not name the alternative tools it replaces or state when not to call it, so it falls short of full when/when-not/alternatives coverage.

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