Skip to main content
Glama

OfferMagnet Jobs

Check visa sponsorship

check_visa_sponsorship
Read-onlyIdempotent

Read a job posting's text and say whether it sponsors visas (yes), refuses sponsorship or requires citizenship/clearance (no), or says nothing (unknown), quoting the deciding sentence.

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": {
      "text": "<text>"
    },
    "name": "check_visa_sponsorship"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe job posting text (paste the whole description).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered. The description adds genuine behavioral value: the three-way output taxonomy, the meaning of each label (refuses sponsorship or requires citizenship/clearance counts as no), and that it returns a quoted deciding sentence. It stops short of describing the exact output shape or handling of ambiguous text.

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?

One sentence, zero filler, and the decision outcomes are front-loaded and enumerated. Nothing is repeated from the title or annotations.

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 single-input classifier with no output schema, the description does the necessary work by defining the label set and the supporting-quote behavior. It leaves the concrete response format unspecified, which is a minor gap but not a blocker for correct invocation.

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 a single parameter at 100% schema description coverage, the schema already explains that the full posting text should be pasted. The description only restates this, adding no formatting or size guidance beyond what the schema provides, so 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?

States a specific verb and resource (read a job posting's text) and the exact decision space it produces: yes / no / unknown, plus a supporting quote. This is clearly distinguishable from siblings like search_jobs or get_job that retrieve rather than classify postings.

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 input context implies usage (you already have the posting text in hand), but the description never says when to pick this over siblings, nor when not to use it — e.g., that it does not fetch postings itself. Guidance is implied rather than 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