Skip to main content
Glama
darthzen

fossa-mcp

by darthzen

fossa_set_license_conclusion

DestructiveIdempotent

Set or remove a license conclusion on a dependency revision to override FOSSA's detected licenses, determining reported licensing issues and attribution.

Instructions

Add a license to, or remove one from, the concluded licenses FOSSA reports for a dependency revision.

WRITES TO FOSSA. action="conclude" requires FOSSA_ALLOW_WRITES=true; action="unconclude" additionally requires FOSSA_ALLOW_DESTRUCTIVE=true, and so does any conclusion at organization or global scope.

A conclusion overrides what FOSSA's scanners detected, so it decides which licensing issues exist and what the attribution report says. scope is required and never defaults: "project" needs project_locator, "revision" needs project_locator and revision_locator, "release_group" needs release_group_id, "release" needs both release ids, "organization" needs organization_id, and "global" is FOSSA-admin only and applies to every organization. Pass origin_id to have FOSSA rescan that revision or release for issues afterwards. Requires Edit permission on the dependency revision.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeYes
actionYes
origin_idNo
license_idYes
release_idNo
organization_idNo
project_locatorNo
release_group_idNo
revision_locatorNo
dependency_revision_locatorYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Beyond the annotations, the description discloses write behavior, env var gates, scope-specific destructive requirements, side effects on attribution and issues, and edit permissions. This provides rich context not inferable from the schema.

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?

The description is dense but well-organized: purpose first, followed by safety warnings and scope parameter rules. Every sentence adds necessary context for a complex multi-scope tool.

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

Completeness5/5

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

The description covers permission needs, side effects, scope rules, rescan behavior, and admin-only scope. Given the 10-param schema and output schema, nothing critical is missing.

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

Parameters5/5

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

Schema coverage is 0%, but the description compensates by explaining each scope value and its required parameters, plus the meaning of origin_id. It clarifies action semantics and permission implications across scopes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence explicitly states the tool adds or removes a license from concluded licenses for a dependency revision. This is a specific verb+resource, setting it apart from sibling tools focused on projects, revisions, issues, etc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use the tool: to override scanner-detected conclusions and affect attribution. It details permission requirements for different actions and scopes, but does not name alternative tools for similar tasks.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/darthzen/fossa-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server