Skip to main content
Glama

scan_asana

Scan Asana tasks and comments to detect leaked secrets (API keys, tokens, passwords). Read-only operation, never modifies Asana data.

Instructions

Read Asana tasks and comments to detect leaked secrets (API keys, tokens, passwords). Never modifies Asana — no tasks or comments are written. Auth: requires an Asana personal access token; set ASANA_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 Asana API rate limits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyYesAsana personal access token (or set ASANA_TOKEN env var)
scopeNoWorkspace or project 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
Behavior1/5

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

The description claims the tool never modifies Asana (read-only), but the annotations set readOnlyHint to false, indicating it is not read-only. This is a direct contradiction, making the description unreliable for behavioral understanding.

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 front-loads the main purpose and covers key details concisely. It could be broken into sections for easier scanning, but it is not overly verbose.

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?

Covers auth, side effects, return format (redacted), and rate limits. An output schema exists but the description does not reference it. Given the tool's complexity and 8 parameters, it is reasonably complete.

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?

Input schema has 100% coverage with descriptions. The tool description adds context beyond the schema, such as explaining the purpose of allow_secret_upload and show_matched_secret_on_logs, and how api_key can be set via env var.

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?

Clearly states it reads Asana tasks/comments to detect leaked secrets, and explicitly says it never modifies Asana. This differentiates it from sibling scanner tools for other platforms.

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?

Provides explicit guidance on when to use (scan Asana for secrets) and what not to do (never modifies). Auth requirements and side effects are mentioned, but it does not explicitly compare with sibling scanners.

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