Skip to main content
Glama

OpenNash Jobs

Research search

search
Read-onlyIdempotent

For deep-research connectors that need search and fetch: free-text search over jobs and companies, returning ids for fetch. For filtered job search (location, company, date, paging) use search_jobs.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault
resultsYes
metadataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / query / maxLength
      Added value: +240
    • addedInput schema / properties / query / minLength
      Added value: +1
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"searchArguments"
    • addedOutput schema / $defs
      Added value: +{
      +  "ResearchDocument": {
      +    "additionalProperties": true,
      +    "properties": {
      +      "id": {
      +        "type": "string"
      +      },
      +      "title": {
      +        "type": "string"
      +      },
      +      "url": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "title",
      +      "url"
      +    ],
      +    "type": "object"
      +  }
      +}
    • addedOutput schema / properties
      Added value: +{
      +  "metadata": {
      +    "additionalProperties": true,
      +    "type": "object"
      +  },
      +  "results": {
      +    "items": {
      +      "$ref": "#/$defs/ResearchDocument"
      +    },
      +    "type": "array"
      +  }
      +}
    • addedOutput schema / required
      Added value: +[
      +  "results",
      +  "metadata"
      +]
    • removedOutput schema / title
      Removed value: -"searchDictOutput"
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine value beyond them by disclosing that results are ids intended to be piped into fetch, implying partial records rather than full objects. It does not mention result caps, ranking, or rate limits.

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 sentences, front-loaded with what the tool is and immediately followed by the routing rule to its sibling. No filler and nothing buried.

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 read tool with full annotations and an output schema, the description covers purpose, routing, and the search-to-fetch workflow. Nothing an agent needs in order 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the param, and it does supply the key semantics: the query is free-text and spans both jobs and companies rather than being an id or exact-match filter. It does not restate the 240-character bound, which the schema already enforces.

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?

Names a specific verb and resource ("free-text search over jobs and companies") and states the output shape ("returning ids for fetch"), which lets an agent distinguish it from search_jobs 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 Guidelines5/5

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

Explicitly frames the use case ("deep-research connectors that need search and fetch") and names the alternative plus the condition that selects it: filtered search by location, company, date, paging belongs in search_jobs. Both the when and the when-not are stated.

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