Skip to main content
Glama
darthzen

fossa-mcp

by darthzen

fossa_get_project_associations

Read-only

Fetch a FOSSA project's labels and release groups, plus last published timestamp on request. Returns per-section data/errors, so empty results are not mistaken for failures.

Instructions

List a project's labels, its release-group memberships, and the timestamp of the last update published for it.

Read-only. Each section is one FOSSA call. By default this fetches "labels" and "release_groups"; name "last_published" in sections to fetch that too. It comes back as a bare ISO timestamp string.

Sections are independent: one failing section does not discard the others. Every section that answered is under data, keyed by section name, and every section FOSSA rejected is under errors with its status code and message. The two keys never overlap, so a section that came back empty (present in data as [] or {}) is distinct from one that failed (absent from data, present in errors). Check errors before concluding a project has no labels or no release groups.

"last_published" is not fetched by default because FOSSA answers it with 404 NotFoundError: Last published date not known for a project that has never had an update published, which is the common case. Treat that particular 404 as "nothing published yet" rather than as a broken call — FOSSA's own message says the date is not known, not that the project or the endpoint is missing. Any other status under errors is a real failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionsNo
project_locatorYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

The description goes far beyond the readOnlyHint and openWorldHint annotations. It discloses detailed behavioral traits: sections are independent, responses are split into 'data' and 'errors' keys, empty results vs failures are distinguished, and the specific 404 for 'last_published' is explained. This is exemplary transparency.

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 well-structured with clear paragraphs and front-loaded purpose. While longer than typical, every sentence provides useful information about behavior, error handling, or usage. It is not padded, though it could be slightly more succinct without losing critical detail.

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 is remarkably complete for a tool with two parameters and an output schema. It explains the response structure, the distinction between empty and failed sections, and the meaning of the 404 error. Given the complexity and absence of schema descriptions, the description fills all necessary gaps.

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

Parameters4/5

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

With schema description coverage at 0%, the description compensates strongly for the 'sections' parameter by explaining each enum value and their effects. However, it does not elaborate on the format or semantics of 'project_locator', leaving a gap for that parameter. Overall, it adds substantial meaning beyond the input schema.

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's function: "List a project's labels, its release-group memberships, and the timestamp of the last update published for it." This uses a specific verb (list) and resource (project associations), distinguishing it from sibling tools like fossa_get_project or fossa_list_projects.

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 clear context on how to use the tool, including how to request the optional 'last_published' section and how to interpret errors. It explains the default behavior and the special 404 case, giving practical guidance. It does not explicitly name alternatives, but the usage context is well established.

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