Skip to main content
Glama

Read applications

get_applications
Read-onlyIdempotent

Applications ready for review, approve-first jobs, every application, each with its match and reply score, totals, replies, one application, its packet (whose preparationId, reviewDigest and authorityDigest apply_to_job needs) and its documents. Actions: ready, approvals, applied, totals, live, replies, get, packet, document, job_page. Call with action "help" for each action's fields.

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": {
      "action": "<action>"
    },
    "name": "get_applications"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoFields for the action. Call with action "help" to list each action's fields.
application_idNoAn application's id from get_applications.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context that packet returns carry preparationId/reviewDigest/authorityDigest consumed by apply_to_job, but says nothing about pagination, result caps, or what totals aggregates — relevant for a list-style read.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is a single dense run-on of comma-separated nouns that is hard to parse, and the second sentence restates the action enum already present in the schema — redundant with structured data. Only the final 'help' sentence is clearly earned; the rest is badly structured rather than efficient.

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

Completeness3/5

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

For a ten-action tool with a free-form nested params object and no output schema, the description does the minimum: it names the actions and points to a help action. It still leaves return shapes and per-action behavior undocumented, which the absent output schema would otherwise require the description to carry.

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 67%, and the description usefully clarifies that 'params' is action-specific and can be enumerated via action "help", which the schema only partially conveys. Against that, the eleven action enum values are listed without any semantic explanation, so the highest-value parameter remains opaque without a follow-up call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description establishes the resource domain (applications, packets, documents) and lists ten action names, so the agent knows it is a multi-action read surface. However, the opening is a verb-less run-on noun list and the action names ('ready', 'live', 'job_page') are never tied to a specific verb or explained, so the agent cannot tell what most actions actually do without calling help.

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?

It gives one concrete routing rule — call action "help" to discover each action's fields — and hints that packet fields feed apply_to_job. It never says when to choose this tool over manage_applications or apply_to_job, nor what distinguishes 'ready' from 'approvals' or 'applied', leaving selection among the ten actions to inference.

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.