PacketFabric

pf_find_locations

Read-only

Find PacketFabric locations / POPs (data center, address, market, status, port types).

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": "pf_find_locations"
  }
}

Input Schema

Name	Required	Description
`pop`	No	POP code, e.g. LAX1.
`city`	No
`state`	No
`fields`	No	Only return these keys from each item (dot paths allowed, e.g. 'interfaces'). Omit for all.
`market`	No	Market code, e.g. LAX.
`region`	No	Region short name, e.g. US, UK.
`any_type`	No	Include non-primary location types.
`max_items`	No	Cap on list items returned.
`nat_capable`	No
`ipsec_capable`	No
`near_cloud_router`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

B3/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the categories of location data available, but it does not disclose pagination behavior, rate limits, or other operational details beyond the output schema.

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 front-loaded sentence with no wasted words. It is concise, though it provides little structure for an 11-parameter search tool.

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

Completeness3/5

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

The output schema and annotations reduce the description's burden, but for an 11-parameter location search, the lack of filter guidance and usage context leaves meaningful gaps. It is minimally adequate for an agent that already understands the PacketFabric location model.

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

Parameters2/5

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

With 11 parameters and only 55% schema description coverage, several filters such as nat_capable, ipsec_capable, near_cloud_router, city, and state are not explained in the description. The description mentions broad data categories but does not map them to parameter semantics or add meaning beyond the schema.

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?

The description gives a specific verb and resource: 'Find PacketFabric locations / POPs.' It also lists the kinds of location data involved, but it does not explicitly distinguish this tool from any sibling.

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?

There is no explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The purpose implies a location search, but usage must be inferred.

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

All PacketFabric tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?