Skip to main content
Glama

list_workspace

Read-only

Retrieve saved resumes, job postings, application goals, search results, and preparation batches to resume your job-application workflow after a restart.

Instructions

读取简历、岗位、已保存求职目标、查找结果与准备批次,重启后可继续使用已有资料。

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": "list_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the safe read-only, non-destructive, closed-world profile, so the description only needs to add context. It does add genuine context: the workspace contents survive a restart and remain reusable, which tells the agent results are durable state rather than session-scoped. It still omits scope details such as whether everything is returned at once or how large the payload can be.

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

Conciseness4/5

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

A single compact sentence that front-loads the resource list and appends the persistence note. Every clause carries information; the only minor cost is that the enumerated list is dense and unpunctuated by structure.

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 covers both what comes back (five named artifact categories) and a key behavioral property (persistence across restarts). Nothing critical is missing, though a note on output shape or volume would make it fully self-sufficient.

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 and the input schema is an empty object, so there is no parameter meaning for the description to supply. The baseline for a parameterless tool applies, with no gaps to compensate for.

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?

The description gives a specific read verb and enumerates the resource types returned: resumes, jobs, saved job-search goals, search results and preparation batches. That makes the payload concrete rather than tautological. It does not explicitly contrast itself with the sibling read/prepare tools, so it stops short of full sibling differentiation.

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 only implied: by listing what is stored and noting that material persists after restart, it hints the tool is used to resume prior work. There is no explicit 'call this when...' statement and no mention of when a more targeted sibling such as review_context or goal_candidates would be preferable.

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