Skip to main content
Glama

Workopia

by io.workopia

dashboard_tool

Read-only

Show the signed-in user's Workopia dashboard (saved, tailored, and applied jobs + latest resume). Requires OAuth. Default action is list; optional status_filter (all | saved | tailored | applied). Use whenever the user asks to recall their Workopia activity: 'my applications', 'what jobs have I saved / applied to / tailored', 'show my dashboard', 'where did I leave off'. Returns a secure link to open the full dashboard on the web.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNo
status_filterNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already mark readOnlyHint=true and destructiveHint=false. The description adds that it requires OAuth and returns a secure link to the web dashboard, providing useful behavioral context beyond the annotations.

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?

The description is four sentences, front-loading the core purpose, then authentication, then usage triggers, then output. Every sentence adds essential information with no wasted words.

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 read-only dashboard tool with no output schema, the description covers purpose, parameters, authentication, and output format. It does not cover error cases or rate limits, but overall is sufficient for an agent to use 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 description coverage is 0%, so the description must compensate. It mentions the optional status_filter with its enum values and the default action, but does not fully describe the action parameter (only that default is 'list'). More detail would improve this dimension.

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 clearly states the tool shows the signed-in user's Workopia dashboard with specific components (saved, tailored, applied jobs + latest resume). It distinguishes from sibling tools like job_detail_tool by focusing on an overview.

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?

The description explicitly provides example user queries that trigger this tool, such as 'my applications' and 'show my dashboard', giving clear when-to-use guidance. It implies alternatives exist for specific job details.

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

All Workopia toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool has a clearly distinct responsibility: dashboard overview, job detail rendering, job search/refine/save, and resume tailoring. The job_tool description explicitly routes detail requests to job_detail_tool, preventing overlap.

Naming Consistency4/5

All tool names use snake_case with a _tool suffix, giving a recognizable pattern. The mix of noun-based names (dashboard_tool, job_tool) and verb-based names (tailor_resume_tool) is a minor inconsistency, and job_tool is more generic than its siblings.

Tool Count5/5

Four tools is well-scoped for a focused job-search and resume-tailoring assistant, and each tool covers a meaningful user workflow. There are no redundant or excessive tools.

Completeness3/5

The core search → detail → save → tailor → dashboard loop is covered, but the descriptions reference resume_tool and cover_letter_tool that are not exposed in the server, creating dead ends for those requests. There are also no unsave/delete or direct apply actions for saved jobs.

Resources