이 프로젝트는 모델 컨텍스트 프로토콜(MCP) 생태계의 일부이며, 외부 API와 상호 작용하고 특정 도메인 모델을 관리하는 도구를 제공합니다. 외부 API 통합 및 데이터 검증 기능을 갖춘 MCP 서버를 구축하는 방법을 보여주기 위해 설계되었습니다.
Related MCP server: Mercado Livre MCP Server
get-acoes : 기본 주식 정보를 가져옵니다.
Zod 를 사용한 입력 검증.
fetch (인프라 계층)를 사용하여 Investidor10 API와 통합합니다.
이 프로젝트는 도메인 주도 설계 (DDD) 패턴에서 영감을 받은 계층형 아키텍처를 따릅니다.
도메인 ( src/domain ): 데이터 구조를 나타내는 인터페이스와 유형을 정의합니다(예: Investidor10 ).
인프라 ( src/infrastructure ): Investidor10 API에 대한 HTTP 호출을 담당하는 Investidor10ApiService 와 같은 외부 서비스를 구현합니다.
애플리케이션 ( src/application ): 인프라에서 데이터를 처리하고 포맷하는 Investidor10Service 의 비즈니스 로직을 포함합니다.
인터페이스 ( src/interface ): MCP 서버에 도구를 등록하고, 검증 스키마를 정의하고, 결과를 반환하는 컨트롤러( Investidor10ToolsController )가 포함됩니다.
진입점 ( src/main.ts ): McpServer 초기화하고, 전송( StdioServerTransport )을 구성하고, 서비스와 컨트롤러를 인스턴스화하고, stdio 에서 수신을 시작합니다.
폴더 구조는 다음과 같습니다.
지엑스피1
git clone git@github.com:newerton/mcp-investidor10.git
cd mcp-investidor10
npm install
npm run buildCtrl+Shift+P 누르고 "MCP: 서버 목록"을 선택하세요.
"주식"을 선택한 다음 "서버 시작"을 선택하세요.
Ctrl+Shift+P 누르고 "MCP: 서버 목록"을 선택하세요.
"주식"을 선택한 다음 "출력 표시"를 선택하세요.
풀 리퀘스트를 환영합니다! 이슈를 공개하고 개선 사항에 대해 논의해 주세요.
이 프로젝트는 MIT 라이선스에 따라 라이선스가 부여되었습니다. 자세한 내용은 LICENSE 파일을 참조하세요.
Buscar informações básicas de ações
| Name | Required | Description | Default |
|---|---|---|---|
| stocks | Yes | Array of stock symbols |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'buscar' (search) which implies a read operation, but doesn't specify whether it's safe, requires authentication, has rate limits, or what format the results come in. This leaves significant behavioral gaps for an agent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence in Portuguese that directly states the tool's purpose without any unnecessary words or structural issues. It's appropriately sized and front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'informações básicas' includes, the format of returned data, error conditions, or any behavioral constraints. The agent would need to guess about the tool's behavior and output.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 100%, with the parameter 'stocks' clearly documented as an array of stock symbols. The description doesn't add any additional parameter semantics beyond what the schema already provides, so it meets the baseline for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Buscar informações básicas de ações' clearly states the tool's purpose as searching for basic stock information, with a specific verb ('Buscar') and resource ('ações'). However, without sibling tools to differentiate from, it cannot achieve a perfect score for sibling differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or contextual constraints. It simply states what the tool does without any usage instructions or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
get-acoesScored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a distinct purpose focused on retrieving basic stock information.
A single tool inherently has consistent naming, as there are no other tools to compare against. The tool name 'get-acoes' follows a clear verb-noun pattern.
One tool is too few for a server named 'Investidor10 MCP Server', which suggests a broader financial or investment domain. This minimal set severely limits functionality and likely indicates significant gaps in coverage.
The server is severely incomplete for an investment domain. With only a tool to get basic stock information, it lacks essential operations like portfolio management, market analysis, transaction execution, or even updates/deletes for financial data.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
brapi.dev MCP — Brazilian stock + crypto + ETF quotes.
Open-source MCP server for Zerodha Kite Connect. Portfolio, market data, backtesting, alerts.
Multi-tenant FastMCP server for Charles Schwab brokerage data, monetized via DPYC Tollbooth
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/newerton/mcp-investidor10'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
