Skip to main content
Glama

BRAINIAC Malware & File Threat Intelligence

Detect macro document risk

file-security_macro-document-risk-detect

Identify suspicious macro markers in caller-supplied Office/RTF documents via static strings/package entries. Macros are never executed. Price $0.04 USDC. POST /api/v1/file-security/macro-document-risk-detect. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "file-security_macro-document-risk-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
filesNo
reportsNo
artifactsNo
maxArchiveDepthNo
maxInflateBytesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does more than most: it discloses that analysis is static only and macros are never executed (a key safety property), the price ($0.04 USDC), and that unpaid calls return 402 and do not run. It omits output shape, rate limits, and any auth detail beyond payment, which keeps it short of a 5.

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?

Four short sentences, front-loaded with purpose and safety before price and endpoint/error behavior. Every sentence carries distinct information; the size is appropriate for the tool's complexity.

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

Completeness2/5

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

For a tool with 10 params, nested objects, no annotations, and no output schema, the description covers purpose, payment, and safety but leaves the entire input contract and return values unexplained. An agent would need to derive the calling shape purely from an undocumented schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 10 parameters including nested file/artifact/report objects, maxArchiveDepth, and maxInflateBytes, and the description says nothing about any of them. Only 'caller-supplied documents' loosely hints that a file body is expected; the bulk of the input surface is undocumented in both places.

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 and target ('Identify suspicious macro markers') and narrows the resource to 'Office/RTF documents' analyzed via 'static strings/package entries', which naturally separates it from archive-payload or script-pattern siblings. It never names an alternative explicitly, so sibling differentiation is inferred rather than stated.

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 scope ('caller-supplied Office/RTF documents') implies when it applies, and 'macros are never executed' implicitly frames it as safe static triage. There is no explicit when-to-use vs when-to-pick-another-tool guidance (e.g., archive payloads or script patterns), so the agent must infer routing.

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