twingate-mcp

Overview Schema Source Related Servers Discussions Admin

list_resources

Read-onlyIdempotent

Retrieves Twingate resources with IDs, names, addresses, remote network names, and active status so you can inventory access targets; check the truncated flag to know if results are capped.

Instructions

List Twingate resources: id, name, address, remote network name, and whether active. Use get_resource_access with an id to see who can reach one. Results are capped by limit; if truncated is true, more existed than were returned, so do not treat the list as complete.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum items to return (server default if omitted).

Output Schema

Name	Required	Description	Default
`items`	Yes
`truncated`	Yes
`total_returned`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 24, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare this as a safe, read-only, idempotent operation, so the description does not need to restate safety. It adds meaningful behavioral detail by explaining the `limit` cap and the `truncated` signal, warning that the list may be incomplete. It does not mention authentication or rate limits, but those are not essential here.

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 compact sentences, front-loaded with the resource and returned fields, then the sibling alternative, then the truncation caveat. Every sentence adds distinct information.

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 tool has an output schema, so the description need not explain return values in depth. It covers the key operational risk (truncated results) and points to the correct sibling for access inspection, making it complete for this simple list operation.

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?

Schema coverage is 100%, so the `limit` parameter is already documented. The description adds value by linking `limit` to truncation behavior and warning not to treat a truncated result as complete.

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 states a specific verb and resource: "List Twingate resources," and enumerates the returned fields (id, name, address, remote network name, active status). It also distinguishes this tool from the sibling get_resource_access by routing access-inspection questions there.

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

Usage Guidelines5/5

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

It explicitly names the alternative tool for a different task: "Use get_resource_access with an id to see who can reach one." It also provides a clear caution about interpreting the list when `truncated` is true, which is essential usage guidance.

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

Deploy Server