Skip to main content
Glama

Moyan Audit — Agent Session Security Audit

moyan_precheck

Single-event security pre-check from a free-text incident description (deterministic feature pre-check; patterns reported by the submitter are marked unverified, unaddressed categories unknown). If the description embeds a structured session record JSON, the full 25-check engine runs instead. Never include passwords, private keys, seed phrases, or production credentials — such input is rejected before execution.

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": {
      "text": "<text>"
    },
    "name": "moyan_precheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesFree-text incident description.
titleNoOptional incident title.
contextNoOptional additional context.
endpointNoOptional target endpoint involved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations to lean on, the description carries real weight: it discloses that the check is deterministic and feature-based, that submitter-reported patterns are marked unverified, that unaddressed categories are reported as unknown, and that secrets/credentials are rejected before execution. The main gap is return shape and cost/latency, which are not described.

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?

Three sentences, front-loaded with the core operation, then the mode-switch condition, then a safety constraint. Dense but every sentence carries information; the parenthetical is slightly compressed to the point of being awkward, but no sentence is padding.

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?

For a tool with no annotations and no output schema, the definition covers execution mode, determinism, verification caveats, and input rejection rules — enough to call it correctly. The notable omission is any hint at what the pre-check returns (findings list, verdict, category coverage), which an agent would want before deciding how to present results.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine semantics beyond the schema: the `text` field is not just free text but may embed a structured session record JSON that switches execution modes — a behavioral meaning the schema does not convey. The other optional fields (title, context, endpoint) get no additional treatment, but the schema already documents them.

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?

The description states a specific verb and resource: a 'single-event security pre-check' built from a 'free-text incident description.' It also clarifies the scope ('single-event,' 'deterministic feature pre-check'), which implicitly contrasts with a broader checkup, but it never names or differentiates against the sibling moyan_checkup, so an agent must infer the split.

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?

Usage is implied by the phrasing 'single-event ... from a free-text incident description,' and the description usefully adds a routing condition: embedded structured session record JSON triggers the full 25-check engine instead. However, there is no explicit when-not guidance and no reference to the sibling tool, so an agent gets the shape of the use case without a firm selection rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources