CNB Remote MCP

Overview Schema Source Related Servers Discussions Admin

List NPC activity

npc_actions

Read-onlyIdempotent

List recorded agent actions (calls, pushes, PRs) in a repository, with filters by event type, agent name, or triggering user.

Instructions

List recorded NPC actions (calls, pushes, PRs) in a repository.

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": {
      "repo": "<repo>"
    },
    "name": "npc_actions"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number, starting at 1
`repo`	Yes	Repository path, e.g. "owner/repo" or "group/subgroup/repo"
`event`	No	Filter by event type
`npc_name`	No	Filter by NPC name
`page_size`	No	Items per page (max 100)
`trigger_username`	No	Filter by triggering user

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 5, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds the scope of the returned data (calls, pushes, PRs) but says nothing about pagination behavior, result caps, or ordering, which is the kind of extra context that would push this above baseline.

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?

One front-loaded sentence with zero filler: verb, resource, and the enumerated action types. Nothing is redundant and nothing needs to be read twice.

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?

With six parameters, full schema coverage, and read-only annotations, most of what an agent needs is present in structured fields. However, for a paginated listing tool with no output schema, the description omits anything about result volume, page navigation, or ordering, leaving the agent to guess at list behavior.

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 description coverage is 100%, and the schema documents each filter (event, npc_name, trigger_username, page, page_size) with examples and bounds. The description only reinforces that the scope is a repository; it adds no filter semantics beyond the schema, so baseline 3 applies.

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?

States a specific verb (List) and resource (NPC actions) and parenthetically enumerates what counts as an action (calls, pushes, PRs), so an agent knows what data comes back. It does not distinguish itself from the closely named sibling npc_search or npc_status, which is the only thing keeping it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of the alternatives. An agent seeing npc_search and npc_status alongside this tool has to infer from names alone that this one is the unfiltered-ish activity listing.

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