Skip to main content
Glama

Get application code security

get_application_code_security
Read-only

Read the source-code security findings for an Application's repository, including the dependency alerts and whether each one has a fixed version available. Read-only.

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": {
      "application_id": "<application_id>"
    },
    "name": "get_application_code_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, and the trailing 'Read-only' merely restates it. The description does add real context about what the payload contains — dependency alerts plus whether a fixed version exists — but says nothing about permissions required, result volume, or pagination for a findings list that could be large.

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 sentence, front-loaded with the verb and resource, with the payload contents appended. No filler, no repetition, and the read-only note is a short trailing clause rather than preamble.

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 one-parameter read tool with annotations covering safety and full schema coverage, the description is nearly sufficient — it names the resource, the scope, and what the findings include. Without an output schema, it could have said a bit more about the shape of the returned findings, but nothing an agent needs to call it correctly is missing.

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?

There is a single required parameter with 100% schema description coverage, so the baseline is 3. The phrase 'an Application's repository' does add a small hint that application_id resolves through to a linked source repository, but no format or sourcing details are added beyond 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 gives a specific verb and resource — reading source-code security findings for an Application's repository — and narrows the scope to dependency alerts and fixed-version availability. This implicitly separates it from siblings such as get_application_container_security and get_application_security_versions, though no sibling is named explicitly.

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 scoping language: use this when you need repository-level code/dependency findings for a specific application. There is no explicit when-to-use or when-not-to-use guidance and no named alternative among the many adjacent security tools (get_security_findings, get_application_container_security), leaving the agent to 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.