AgentsID Guard

Official

by AgentsID-dev

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

process_info

Obtain detailed information about a specific process using its PID, requiring process.read permission.

Instructions

Get detailed info about a specific process. Requires process.read permission.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pid": "<pid>"
    },
    "name": "process_info"
  }
}

Input Schema

Name	Required	Description	Default
`pid`	Yes	Process ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly mentions the required 'process.read permission', which is useful. However, it does not explicitly state that the operation is read-only (no side effects), nor does it describe behavior for non-existent processes or potential errors. This is a partial disclosure.

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 a single, concise sentence that front-loads the action and target, then adds the permission requirement. No unnecessary words or repetition.

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 simple one-parameter schema and no output schema, the description adequately states the purpose but leaves gaps: it does not describe the return format ('detailed info' is vague), nor error conditions or prerequisites beyond permission. This is sufficient for a minimal tool but not fully comprehensive.

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 already provides 100% coverage for the 'pid' parameter with its description 'Process ID'. The tool description adds no additional meaning about the parameter beyond what the schema already states, so the baseline score of 3 applies.

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 action ('Get detailed info') and the target ('a specific process'), distinguishing it from sibling tools like process_list (which lists processes) and process_kill (which terminates processes). It is specific and uses a verb+resource structure.

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 implies usage: when you have a specific PID and need details. However, it does not explicitly mention alternatives or when not to use this tool, such as using process_list to find PIDs first. No exclusions or alternative tool references are provided.

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