Skip to main content
Glama
darthzen

fossa-mcp

by darthzen

fossa_get_snippet

Read-only

Retrieve a single code snippet match from FOSSA, showing its upstream package, licenses, issue counts, and matched file paths. Optionally include the matched source lines and reference/detected text for detailed analysis.

Instructions

Show one matched snippet: the upstream package it came from, its licenses, its issue counts, and every file path it was matched in.

Read-only. Pass path to hydrate the match details for that file. Set include_match_details=True (which needs path) to also fetch the matched source lines themselves — the reference text and the detected text.

Match details are capped at FOSSA_REPORT_MAX_CHARS. When the cap bites, match_details is returned as truncated JSON text rather than an object, with truncated set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNo
snippet_idYes
project_locatorYes
revision_locatorYes
include_match_detailsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

The description adds valuable behavioral context beyond the readOnlyHint annotation, including the FOSSA_REPORT_MAX_CHARS cap and the truncated JSON fallback behavior. It also clarifies that include_match_details requires path. No contradictions with annotations.

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 well-structured, front-loaded with the primary purpose, and every sentence adds important detail (including the truncation behavior). It is appropriately sized for the tool's complexity.

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 the tool's main return values, optional parameter behavior, and an important edge case (truncation). Given the output schema exists and the tool is read-only, this is a complete and self-sufficient description.

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?

The schema has 0% description coverage, so the description must compensate. It thoroughly explains the optional path and include_match_details parameters and their relationship, but does not clarify the required project_locator, revision_locator, and snippet_id beyond their names. This partial compensation warrants a mid-range score.

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 description clearly states the tool shows a single matched snippet with specific details (upstream package, licenses, issue counts, file paths), distinguishing it from the sibling fossa_list_snippets which would list snippets. The verb 'Show' and specific resource make the purpose unambiguous.

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 provides context on when to use this tool—when you need details for a specific snippet—and gives clear guidance on optional parameters (path, include_match_details). It does not explicitly name alternative tools or exclusion criteria, so it stops short of a perfect score.

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