Skip to main content
Glama

protools_code_review_start

Initiate asynchronous code review. Returns task ID to query progress or retrieve partial results.

Instructions

启动异步代码审查任务,返回任务 ID 并支持查询进度或获取部分结果。

重要:审查结果需要批判性分析

  • 不是所有报告的问题都需要修复,需根据项目实际情况判断

  • 区分真正的问题 vs 过度工程化建议(如"建议添加更多配置")

  • INFO 级别通常可忽略,MINOR 需权衡成本,MAJOR/CRITICAL 才是重点

  • 如果多个模型报告相同问题,可信度更高

高效等待(避免轮询)

  • 设置较大的 wait_first_result_ms(如 60000)一次性等待首个结果

  • 或在查询 status 前用 Bash sleep 间隔等待(如 sleep 15)

  • 不要疯狂轮询 status,每次调用都消耗 token

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNo工作目录,多仓库工作区时指定要审查的项目路径(如 /home/user/Work/xxxx)
modeNo代码压缩模式:full=完整代码 | compact=移除注释和import | skeleton=仅保留类/方法签名(适合全仓库审查)compact
focusNo审查关注领域:security | performance | quality | maintainability | allall
inputsNo要审查的文件/目录/glob 路径列表(与 git_mode 二选一)
outputNo输出方式:inline=直接返回 | file=写入文件inline
contextNo附加的审查上下文或特殊说明
excludesNo排除的 glob 模式,如 ["**/test/**", "**/*.test.ts"]
git_modeNoGit diff 模式:staged=已暂存 | unstaged=未暂存 | all=全部未提交
providerNoLLM Provider,默认从 LLM_PROVIDER 环境变量读取
providersNo并发审查使用的 provider 列表,默认使用 LLM_PROVIDER
extensionsNo过滤扩展名,如 [".ts", ".js"]
output_dirNo输出目录(output=file 时使用)
include_full_filesNoGit diff 模式下,是否同时包含变更文件的完整内容以提供更好的上下文
wait_first_result_msNo等待首个模型结果的超时时间(毫秒),0 表示立即返回
include_project_contextNo是否包含项目信息(package.json、目录结构等)以帮助模型理解项目背景
Behavior4/5

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

Discloses async behavior, result interpretation (critical analysis needed), and polling costs. With no annotations, the description carries full burden and adequately communicates behavioral traits.

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

Conciseness3/5

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

The description is longer than necessary with multiple sections, but it is well-structured and includes important usage tips. It could be more concise without losing essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (15 parameters, async execution) and lack of output schema, the description provides high-level usage patterns but fails to specify the exact return format (e.g., task ID structure). Completeness is adequate but not thorough.

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 input schema covers 100% of parameters with descriptions; the tool description adds no additional parameter insights beyond what the schema already provides. Baseline 3 is appropriate.

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 starts an asynchronous code review task and returns a task ID. It distinguishes itself from sibling tools like protools_code_review (likely synchronous) and protools_code_review_status (for progress queries).

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 efficient waiting strategies (e.g., using wait_first_result_ms or sleep) and warns against polling. However, it does not explicitly state when to prefer this over the sync variant or other alternatives.

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/hotic/protools'

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