Skip to main content
Glama

Import a website's software

import_software
Idempotent

Tells the monitor what software the website and its server run, so their vulnerabilities are checked. Send a file's contents (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lock, mix.lock, composer.json/.lock, requirements.txt, Pipfile.lock, poetry.lock, Gemfile.lock, go.mod, Cargo.lock, pom.xml, .csproj, Dockerfile, docker-compose.yml, .nvmrc, .bun-version, .tool-versions, mise.toml, railpack.json) or a plain list with one item per line as "name version", for example "Debian 12", "nginx 1.24.0", "PHP 8.2.12", "wp-plugin:woocommerce 9.3.3", "npm:lodash 4.17.21". If you can run commands on the server, cat /etc/os-release, nginx -v, php -v and the like give exact versions. Importing the same filename again replaces what it added. Lines that name nothing known are returned as unrecognized. Format and supported files: https://upheron.com/docs/software. Free.

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": {
      "id": "<id>",
      "content": "<content>"
    },
    "name": "import_software"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMonitor ID from list_monitors.
nameNoA label such as frontend/package.json, to keep two files with the same name apart. Importing under the same label again replaces it. Defaults to the filename.
contentYesThe file's text, or the list.
filenameNoThe file's name, such as package-lock.json or Dockerfile; tells the format. Leave out for a plain list.

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?

Annotations already declare write (readOnlyHint=false), idempotent=true, and non-destructive, and the description usefully sharpens the idempotency claim by scoping it to the filename/name label ('importing the same filename again replaces what it added'). It also discloses that unknown lines are returned as 'unrecognized' and notes the operation is free. It says nothing about permissions, rate limits, or what a successful import reports beyond the unrecognized case, so it adds context without fully covering the mutation's behavior.

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 purpose and the 'so vulnerabilities are checked' payoff come first, followed by the two input modes and then the command-line hint. The long parenthetical file list is dense but each entry is functional, since it defines accepted formats. Only the trailing docs URL is arguably expendable.

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?

There is no output schema, so the description carries the return-value burden and does so partially by explaining that unmatched lines come back as 'unrecognized'. Combined with the replacement semantics and the accepted-format enumeration, an agent has enough to call it correctly. Minor gaps remain around error cases and what a successful import returns when everything is recognized.

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?

Schema description coverage is 100%, so all four parameters are already documented, establishing a baseline of 3. The description does add real value for `filename` by enumerating the supported formats (package-lock.json, yarn.lock, go.mod, Dockerfile, .tool-versions, etc.) and for `content` by giving the 'name version' line format with concrete examples like 'wp-plugin:woocommerce 9.3.3'. It still doesn't explain how `id` relates to list_monitors beyond the schema's own note, so the gain is moderate rather than decisive.

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?

States a specific verb and resource: it tells the monitor what software the website and its server run so their vulnerabilities get checked. That is far more informative than the title alone and pins down the downstream effect. It does not, however, name or contrast with the sibling scan_website_software, so an agent must infer which of the two to reach for.

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?

Gives clear situational context: send a lockfile/manifest's contents, or a plain 'name version' list, and if you can run commands on the server, use `cat /etc/os-release`, `nginx -v`, `php -v` to get exact versions. That tells the agent exactly when this tool is the right vehicle. It stops short of explicit exclusions or naming the scanning alternative for cases where no file is available.

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