Skip to main content
Glama
Ringer

warp-mcp

by Ringer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Resubmit a port-in request

port_resubmit_request

Resubmit a rejected or errored port request after fixing the reported issues, moving it out of an error, rejection, or exception state into a valid retry.

Instructions

Resubmit a port that is in an error/rejection/exception state (e.g. after fixing issues with port_auto_fix or port_set_group_details). Only valid from those states — a CONFLICT is returned otherwise. Errors: NOT_FOUND, CONFLICT, TNIQ_ERROR.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPort request UUID (from port_list_requests or port_create_request)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.1/5.0
Behavior3/5

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

Description adds state constraints and error conditions beyond annotations. Annotations already indicate not read-only and not destructive, so description provides moderate additional behavioral context.

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?

Two concise sentences plus error list. Every sentence adds value; no fluff. Front-loaded with action and state constraint.

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?

Given simple tool with one parameter and no output schema, description is complete: covers purpose, allowed states, errors, and references prior tools.

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 for 'id' is already clear and 100% covered. Description adds no further parameter semantics beyond schema.

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?

Clearly states verb 'Resubmit' and resource 'port-in request' in error/rejection/exception state. Distinguishes from siblings by referencing port_auto_fix and port_set_group_details as prior steps.

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?

Explicitly states valid only from error/rejection/exception states with CONFLICT otherwise. Lists error types. Does not explicitly exclude alternative tools like port_submit_request but context makes it clear.

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