Skip to main content
Glama

get-organization-switch-ports-by-switch

Retrieve all switch ports in an organization organized by switch. Filter by criteria like MAC, serial, or network to find specific port configurations.

Instructions

List the switchports in an organization by switch. (read-only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID
perPageNoThe number of entries per page returned. Acceptable range is 3 - 50. Default is 50.
startingAfterNoA token used by the server to indicate the start of the page. Often this is a timestamp or an ID but it is not limited to those. This parame
endingBeforeNoA token used by the server to indicate the end of the page. Often this is a timestamp or an ID but it is not limited to those. This paramete
configurationUpdatedAfterNoOptional parameter to filter items to switches where the configuration has been updated after the given timestamp.
macNoOptional parameter to filter items to switches with MAC addresses that contain the search term or are an exact match.
macsNoOptional parameter to filter items to switches that have one of the provided MAC addresses.
nameNoOptional parameter to filter items to switches with names that contain the search term or are an exact match.
networkIdsNoOptional parameter to filter items to switches in one of the provided networks.
portProfileIdsNoOptional parameter to filter items to switches that contain switchports belonging to one of the specified port profiles.
serialNoOptional parameter to filter items to switches with serial number that contains the search term or are an exact match.
serialsNoOptional parameter to filter items to switches that have one of the provided serials.
fieldsNoReturn only these top-level fields; omit for all. Available: mac, model, name, network, ports, serial.
Behavior2/5

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

The description only notes 'read-only', but with no annotations, it should disclose behaviors such as pagination, filtering behavior, or whether it returns all ports at once. It does not describe the structure of the response or any side effects.

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 a single sentence that gets to the point. It is front-loaded with the key action and resource. However, given the complexity (13 parameters), a bit more structure could improve readability.

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

Completeness2/5

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

With 13 parameters, no output schema, and no annotations, the description is too sparse. It fails to explain return format, pagination, or filtering details that are not already in the schema. Sibling tools add competition that is not addressed.

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 coverage is 100%, so the description does not need to add much. It adds no extra meaning beyond the schema; the baseline score of 3 is appropriate.

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 action ('List'), the resource ('switchports'), and the scope ('in an organization by switch'). The '(read-only)' tag further clarifies its nature, making it specific and distinct from mutation tools.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'get-organization-switch-ports-statuses-by-switch' or 'switch-list-ports'. The description lacks explicit when-to-use, when-not-to-use, or mention of comparable tools.

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/Flagler-County-BoCC/mcp-meraki'

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