Skip to main content
Glama
Sign In
flow-team-mcp

flow-team-mcp

by baekbeombyeon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Flow endpoint metadata

get_flow_endpoint

Retrieve the OpenAPI path, HTTP method, and documentation URL for a Flow endpoint using its ID.

Instructions

엔드포인트 ID로 Flow OpenAPI 경로, HTTP 메서드, 문서 URL을 조회합니다.

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": {
      "id": "<id>"
    },
    "name": "get_flow_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It conveys that this is a read-only lookup ('조회합니다') and specifies the returned fields, but it does not disclose potential errors, permissions, rate limits, or side effects. It is adequate but not rich.

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 states the action and target. It contains no filler or redundant information, making it highly concise and easy to parse.

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 simplicity (1 parameter, no output schema, no annotations), the description covers the essential aspects: what it does, what it returns, and what the parameter means. It lacks explicit usage guidance but is otherwise complete for a straightforward lookup tool.

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?

The description explicitly states '엔드포인트 ID로' (by endpoint ID), giving semantic meaning to the single 'id' parameter beyond the raw schema. Since schema description coverage is 0%, this is valuable and clarifies what kind of identifier is expected.

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 uses a specific verb '조회합니다' (retrieves) and identifies the exact resource: Flow OpenAPI path, HTTP method, and document URL by endpoint ID. This clearly distinguishes it from sibling tools like list_flow_endpoints (listing) and flow_request (executing).

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

Usage Guidelines3/5

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

The description implies usage when you have a specific endpoint ID and need its metadata, but it does not explicitly mention when to use this versus list_flow_endpoints or alternatives. No when-not conditions or alternative tool names are provided, so guidance remains implicit.

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