Skip to main content
Glama
Sign In

mcp

by com.datronis
OverviewDiscussionsAdmin

get_my_applications

Check the status of the authenticated user's job applications. Requires a personal access token (generate one at /app/api-keys/).

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_my_applications"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1)
limitNoResults per page (default: 20)
api_keyNoYour Datronis personal access token (starts with "dtk_"). Generate one at /app/api-keys/. Required unless sent as an `Authorization: Bearer <token>` HTTP header instead (preferred — see search_jobs' api_key description for why).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Your Datronis personal access token (starts with \"dtk_\"). Generate one at /app/api-keys/."New value: +"Your Datronis personal access token (starts with \"dtk_\"). Generate one at /app/api-keys/. Required unless sent as an `Authorization: Bearer <token>` HTTP header instead (preferred — see search_jobs' api_key description for why)."
    • removedInput schema / required
      Removed value: -[
-  "api_key"
-]
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the token requirement and the user-scoped nature, but does not mention behavior like pagination, error responses, or whether the token can be supplied via header (though the schema covers that). The read-only nature is implied by 'check status' but not stated explicitly.

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 concise sentences, front-loaded with the core purpose. Every word earns its place, and the auth note is relevant and actionable.

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 simple paginated list tool, the description covers purpose, scope, and a key prerequisite. No output schema exists, but the description doesn't need to detail returns for such an operation; the auth and user-scope context is sufficient for an agent to invoke correctly.

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 the baseline is 3. The description repeats the token requirement already present in the api_key parameter description but adds no new meaning for page or limit beyond what the schema provides.

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 uses a specific verb and resource: 'Check the status of the authenticated user's job applications.' It clearly identifies the operation and scope, distinguishing it from siblings like apply_to_job (action) and search_jobs (searching all jobs).

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 provides clear context: this tool is for the authenticated user's own applications and requires a personal access token. It doesn't explicitly name alternatives or exclusions, but the scope is unambiguous and no sibling tool overlaps directly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources