Skip to main content
Glama

scan_wrike

Scan Wrike tasks and comments to detect leaked secrets like API keys and passwords. Returns a redacted report without exposing raw secret values.

Instructions

Read Wrike tasks and comments to detect leaked secrets (API keys, tokens, passwords). Never modifies Wrike — no tasks or comments are written. Auth: requires a Wrike permanent access token; set WRIKE_TOKEN env var or pass api_key directly. Side effects: a redacted scan report is uploaded to the n0s1 backend; set allow_secret_upload=True to also upload AES-encrypted secret values for AI validation. Returns redacted findings — raw secret values are never included in the output. Subject to Wrike API rate limits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyYesWrike permanent access token (or set WRIKE_TOKEN env var)
scopeNoFolder or space scope filter
report_formatNoOutput report formatn0s1
show_matched_secret_on_logsNoInclude redacted secret snippets in logs (default: false)
ai_analysisNoQueue async AI credential validation after the scan (requires n0s1 Pro)
n0s1_api_keyNon0s1 API key; overrides the N0S1_TOKEN env var
allow_secret_uploadNoUpload AES-encrypted secret values to the n0s1 backend for AI validation (default: false)
report_uuidNoUUID to assign to the scan report; overrides the auto-generated one

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
report_uuidYes
statusYes
summaryYes
findingsNo
next_cursorNo
usageYes
ai_analysis_statusNo
Behavior5/5

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

The description transparently discloses read-only behavior on Wrike, upload side effects to n0s1 backend, AES encryption option, redacted output, and rate limits. This goes well beyond annotations (destructiveHint=false, openWorldHint=true) by explaining the actual side effects and security considerations.

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?

The description is a single paragraph that efficiently conveys purpose, auth, side effects, and output behavior. It is front-loaded with the main action. Slightly more structured formatting (e.g., bullet points) could improve skimmability, but it is still concise and informative.

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 the complexity of the tool (8 parameters, output schema exists, siblings are other platform scans), the description covers purpose, auth, side effects, rate limits, redacted output, and AI validation. It is complete without needing to repeat output schema details.

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 has 100% description coverage for 8 parameters, so baseline is 3. The description adds context for 'api_key' (set env var or pass directly) and 'allow_secret_upload' (AES encryption for AI validation), but does not elaborate on other parameters like 'scope' or 'report_format' 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 clearly states the tool reads Wrike tasks and comments to detect secrets. It specifies the resource (Wrike) and action (scan for leaked secrets), distinguishing it from sibling tools that scan other platforms like Asana, GitHub, etc.

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?

The description provides auth instructions and states the tool does not modify Wrike, but it lacks explicit guidance on when to use this tool versus alternatives or when not to use it. Usage context is implied (e.g., for Wrike secret scanning), but no exclusions or comparisons with siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/spark1security/n0s1-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server