Skip to main content
Glama
Sign In
Workato Dev MCP

Workato Dev MCP

by gmunro-lyft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_mcp_server_policies

Retrieve rate, quota, and IP policies for an AI Hub MCP server using its handle. Requires MCP privilege.

Instructions

Get an AI Hub MCP server's rate/quota/IP policies by handle. Needs the MCP privilege.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "handle": "<handle>"
    },
    "name": "get_mcp_server_policies"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the transparency burden. It explicitly states the operation is a 'Get' (implying non-destructive) and discloses the privilege requirement, adding useful context beyond the tool name. It does not detail error conditions or output format, but for a simple read operation this is adequate.

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?

The description is a single, front-loaded sentence that efficiently states the purpose and a prerequisite. No redundant words or fluff.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers the essential elements: what is retrieved, the identifier, and the required privilege. It does not explain return values, but that is not required when no output schema exists and the operation is straightforward.

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?

The schema provides only a 'handle' string with no description, and schema description coverage is 0%. The description says 'by handle', which clarifies the parameter's role but adds minimal meaning beyond the parameter name. It does not explain what a handle is, its format, or how to obtain it.

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 tool retrieves policies (rate/quota/IP) for an AI Hub MCP server using a handle. This specific verb+resource distinguishes it from siblings like get_mcp_server or list_mcp_servers.

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?

The description gives clear context: use this tool when you need rate/quota/IP policies for a specific MCP server, identified by handle. It also notes the required MCP privilege, but does not explicitly contrast with alternatives or state when not to use it.

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