Skip to main content
Glama

BirJob

List tracked applications

get_applications
Read-onlyIdempotent

List the user's tracked applications on BirJob, most recently changed first, optionally by status. Use this when the user asks where they applied or how their applications stand. Do not use for saved jobs (get_saved_jobs). Needs a signed-in BirJob job seeker account: the first call asks the user to sign in to BirJob and allow access.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_applications"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page, 1 to 50 (default 1), 10 a page.
statusNoOnly applications with this status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds information annotations cannot: the default sort order and, critically, that the first call triggers an OAuth-style sign-in prompt for a BirJob job seeker account — a real runtime behavior an agent must anticipate. It stops short of describing return shape or pagination behavior beyond what the schema says.

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 tight sentences: scope/ordering first, then usage trigger, then exclusion and auth prerequisite. Nothing is repeated and every sentence carries a distinct decision-relevant fact.

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 two-parameter read tool with full schema coverage and no output schema, the description covers scope, ordering, filtering, alternatives, and the sign-in prerequisite — everything an agent needs to call it and to explain the auth prompt to the user.

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 coverage is 100%, so both parameters (page with 1-50 bounds and 10-per-page, status enum) are fully documented structurally. The description only restates that status filtering is optional and that results are ordered by recency; it adds no syntax or semantics beyond the schema. 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 ('List the user's tracked applications'), adds ordering ('most recently changed first') and an optional filter ('optionally by status'), and explicitly contrasts with get_saved_jobs. An agent can distinguish this from every sibling without opening the 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?

Gives an explicit use trigger ('when the user asks where they applied or how their applications stand') and an explicit exclusion with the correct alternative named ('Do not use for saved jobs (get_saved_jobs)'). Both the when and the when-not are covered.

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