Skip to main content
Glama

AceRound AI Interview Copilot

get_job_intent

Read-only

Show the user's job preferences remembered by the apply assistant: target and excluded companies, company size, directions, employment types, cities, batches, and other notes. (Requires the user's sign-in with scope job_applications:read.)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally; the description adds the auth scope requirement, which is genuinely new information not in any structured field. It also clarifies that this is persisted state owned by the apply assistant, telling the agent results reflect stored preferences rather than a live query. It does not describe behavior when no preferences exist, which keeps it from a 5.

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 front-loaded sentence states the action, the object, and the returned fields, with the auth prerequisite consigned to a parenthetical. Every listed field earns its place because no output schema exists to document them otherwise, and there is no filler.

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 zero-parameter, read-only tool with no output schema, the description carries the right load: it enumerates return content and discloses the auth scope. The only gap is the empty-state behavior, which matters for a preferences object that may be unset for a new user.

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?

The tool takes zero parameters, so there is nothing to disambiguate and the baseline is 4. The description correctly avoids inventing input semantics and instead spends its words on what the tool returns.

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

Purpose4/5

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

States a specific verb and resource: "Show the user's job preferences remembered by the apply assistant," then enumerates the exact data domains returned (companies, size, directions, employment types, cities, batches, notes). It never names update_job_intent, so read-vs-write differentiation is left to the verb, which keeps it just short of a 5.

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?

Usage is implied by the verb "Show" and the object "preferences," and the description supplies one real prerequisite (sign-in with scope job_applications:read). It gives no explicit when-to-use framing and does not tell the agent to prefer update_job_intent for writes or get_campus_job_filters for the campus-filter variant, so guidance stays at the implied level.

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