Skip to main content
Glama

Workopia — Job Search

by io.github.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.3/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds value by stating 'Requires OAuth' and explaining the default action (list) and status_filter options. It also mentions returning a secure link, providing 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 very concise, with only four sentences, each serving a purpose: stating what it does, authentication requirement, default and optional filter, usage examples, and output type. No wasted words.

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?

Given no output schema, the description covers return value (secure link), required auth (OAuth), default and optional parameters, and example use cases. This is sufficient for an agent to understand the tool's functionality and when to invoke it.

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?

The schema has two parameters (action, status_filter) with enums. The description mentions status_filter and its values, adding meaning beyond the schema. However, schema coverage is 0%, and the description does not explain the 'action' parameter beyond its default value, leaving some ambiguity.

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 user's Workopia dashboard including saved, tailored, and applied jobs plus resume. It provides specific query examples like 'my applications' and 'show my dashboard', distinguishing it from sibling tools that handle individual job details, cover letters, or resume tailoring.

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?

The description explicitly lists when to use the tool (e.g., 'my applications', 'what jobs have I saved') and mentions the default action and optional filter. It does not explicitly exclude use cases, but the provided examples and sibling context make the scope clear.

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

All Workopia — Job Search 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.1/5.0
Disambiguation4/5

The four tools serve clearly distinct purposes: dashboard overview, job search/refine/save, job detail rendering, and resume tailoring. job_tool and job_detail_tool could be confused by name alone, but the descriptions explicitly route detail requests to job_detail_tool.

Naming Consistency3/5

All names use snake_case and share the '_tool' suffix, but there is no consistent verb_noun pattern: dashboard_tool, job_detail_tool, and job_tool are noun phrases while tailor_resume_tool is the only verb-led name. The pattern is readable but mixed.

Tool Count5/5

Four tools is well-scoped for a job-search assistant. Each tool covers a distinct user need—searching, viewing details, viewing the dashboard, and tailoring a resume—without unnecessary bloat.

Completeness3/5

Core workflows are covered: search, refine, save, view details, dashboard, and resume tailoring. However, the descriptions reference resume_tool and cover_letter_tool which are not present in the tool set, creating potential dead ends and notable gaps in the advertised surface.

Resources