Skip to main content
Glama

Review application dependency advisories

get_project_security
Read-onlyIdempotent

Returns the authorized project’s application dependency findings from its last scanned deployment, including coverage and advisory status.

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": {
      "project_id": "<project_id>"
    },
    "name": "get_project_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesExact stable project ID. Resolve it first. Never invent an update target.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the genuinely useful constraint that results come only from the LAST scanned deployment and include coverage plus advisory status. However, it does not say what happens when no scan exists, whether stale results are returned, or how coverage is computed – real behavioral gaps for a security-review tool.

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?

A single sentence with no filler, front-loaded with the verb and the object of the operation. Every clause (project scoping, last-scan freshness, coverage and advisory status) carries information an agent needs.

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?

The tool is simple – one required parameter, no nesting, no output schema – and the description covers the safety profile via annotations and the data source. But with no output schema, the return shape is only gestured at ("coverage and advisory status") without field-level detail, and the no-scan/empty-result case is unaddressed.

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?

Only one parameter, with 100% schema description coverage that already states the exact pattern, the need to resolve it first, and the warning never to invent a target. The description adds no project_id semantics beyond the schema, so the baseline of 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?

Specific verb and resource: "Returns the authorized project's application dependency findings from its last scanned deployment." It names the data domain (dependency advisories) and the scope (single project, most recent scan), which separates it from the deployment/project CRUD siblings. It stops short of explicitly naming a sibling it displaces, so it lands at 4 rather than 5.

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: an agent can infer this is the tool for reviewing dependency advisories for one project. There is no explicit when-to-use or when-not-to-use statement, no pointer to the deployment siblings that might also be relevant, and no note about needing a prior scan's existence. Minimum viable routing guidance only.

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