Skip to main content
Glama
Sign In
F6 ASM MCP Server

F6 ASM MCP Server

Official
by F6-Security
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

asm_list_companies

Read-onlyIdempotent

Lists companies accessible to the token and verifies ASM base URL, credentials, and access. Use it first to retrieve company IDs for other tools.

Instructions

Companies this token may read: GET /api/v2/companies. Each entry has id (the company_id of every other tool), name, website, score, footprint (number of domains and IPs) and the recent score history. Call it first: it confirms ASM_BASE_URL, the token and access.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "asm_list_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and open-world semantics, and the description adds meaningful behavior beyond them: it discloses the return payload shape (id, name, website, score, footprint, history) and that the call doubles as a credential/endpoint validation step. Pagination or result-size limits are not mentioned, keeping it from a 5.

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?

Three tight sentences: resource and endpoint first, payload contents second, calling order and purpose third. Every clause carries information an agent needs; there is no filler or restatement of the name.

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?

With no output schema, the description correctly compensates by listing returned fields, and it explains the tool's role as a connectivity/authorization check. It omits whether results are paginated or bounded, which is the only notable gap for a listing tool.

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?

The tool takes zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description usefully clarifies that the returned 'id' is the company_id consumed by every other tool, which is a semantic link the empty schema cannot express.

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 resource and scope: 'Companies this token may read' mapped to GET /api/v2/companies, and enumerates the returned fields. It does not explicitly contrast with siblings like asm_assets_summary or asm_get_assets, but the scope ('this token may read') is distinctive enough to distinguish it in practice.

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?

'Call it first: it confirms ASM_BASE_URL, the token and access' gives explicit ordering and a concrete reason to invoke it before other tools. It stops short of naming when NOT to use it or which sibling supersedes it, so it falls short of a 5.

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

Deploy Server

Other Tools