Skip to main content
Glama
Sign In
armorcode-mcp

armorcode-mcp

by raviraj-ntp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Finding

armorcode_get_finding

Retrieve complete details of a security finding by its ID for efficient triage and analysis.

Instructions

Full finding details by ID.

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": {
      "findingId": "<findingId>"
    },
    "name": "armorcode_get_finding"
  }
}

Input Schema

NameRequiredDescriptionDefault
findingIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

The description is minimal; it does not disclose behavioral traits such as read-only nature, authorization requirements, or whether it returns a full object. No annotations are present to fill the gap.

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?

The description is extremely concise at one sentence. It is front-loaded with the core purpose, but omits valuable context that could be added without sacrificing brevity.

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?

Given no output schema and many sibling tools, the description should indicate what 'full details' includes or how the response is structured. The current text is too vague to fully inform an agent's decision.

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 coverage is 0%, but the parameter 'findingId' with type integer and exclusiveMinimum is self-explanatory. The description adds 'by ID' which confirms usage but provides no additional semantic detail over the schema.

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 'Full finding details by ID' clearly states the verb ('get') and resource ('finding'), and implies retrieval by ID. It distinguishes from sibling tools like 'armorcode_search_findings' (list/search) but does not explicitly explain the scope or uniqueness.

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?

No guidance on when to use this tool versus alternatives like 'armorcode_search_findings' or 'armorcode_get_finding_events'. No when-not-to-use or prerequisite information provided.

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

Deploy Server

Other Tools