tossinvest-openapi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_api_overviewA | START HERE. Returns a high-level map of the Toss Securities Open API: title, version, base server URL, the authentication model, and every category (tag group). Call this first to orient yourself, then drill down with |
| list_categoriesA | Lists every API category (OpenAPI tag) with its display group, endpoint count, and description. Use the category name as the |
| list_endpointsA | Lists endpoints as |
| search_endpointsA | Keyword search across operationId, path, summary, description and tags. Returns the best-matching endpoints ranked by relevance. Use this when you don't know the exact category or operationId. Example queries: 'place order', 'current price', 'holdings', 'exchange rate'. |
| get_endpointA | Returns full detail for ONE endpoint: summary, description, auth requirement, parameters, request body schema, and response schemas with examples. Identify the endpoint either by |
| list_schemasA | Lists the data model (schema) names defined by the API. Pass |
| get_schemaA | Returns the field tree of one data model: field names, types, required flags (marked with *) and descriptions. Nested objects and arrays are expanded; recursive refs are shown as |
| get_integration_guideA | Returns a task-oriented walkthrough for a common use case: the concepts involved plus the recommended, ordered sequence of real endpoints to call. Prefer this over reading endpoints one by one when you want to accomplish an end-to-end task. |
| generate_code_sampleA | Generates a ready-to-adapt request snippet for one endpoint, with the right URL, headers (auth / account), path/query placeholders and request-body example pre-filled. Choose the language; defaults to curl. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: code generation, API overview, endpoint detail, integration guide, schema detail, category listing, endpoint listing, schema listing, and keyword search. No two tools overlap in functionality, and descriptions clearly differentiate them.
All tool names use a consistent verb_noun pattern in snake_case (e.g., generate_code_sample, list_endpoints, search_endpoints). The verbs are either 'get', 'list', 'generate', or 'search', and the pattern is uniform across all 9 tools.
With 9 tools, the set is well-scoped for an API exploration assistant. Each tool contributes to a specific aspect of the workflow (overview, categorization, endpoint details, schemas, search, integration guides, code generation), without being too many or too few.
The tool surface covers the full lifecycle of discovering and understanding an OpenAPI specification: from high-level overview to category listing, endpoint listing and detail, schema listing and detail, keyword search, integration guides, and code sample generation. There are no obvious gaps for the stated purpose.