该项目是模型上下文协议 (MCP) 生态系统的一部分，提供与外部 API 交互和管理特定领域模型的工具。它旨在演示如何构建具有外部 API 集成和数据验证功能的 MCP 服务器。
Related MCP server: Mercado Livre MCP Server
get-acoes ：获取基本股票信息。
使用Zod进行输入验证。
使用fetch （基础设施层）与 Investidor10 API 集成。
该项目遵循受领域驱动设计（DDD）模式启发的分层架构：
域（ src/domain ）：定义表示数据结构的接口和类型（例如， Investidor10 ）。
基础设施（ src/infrastructure ）：实现外部服务，例如Investidor10ApiService ，负责对 Investidor10 API 进行 HTTP 调用。
应用程序（ src/application ）：包含Investidor10Service中的业务逻辑，用于处理和格式化来自基础设施的数据。
接口（ src/interface ）：包括在 MCP 服务器中注册工具、定义验证模式和返回结果的控制器（ Investidor10ToolsController ）。
入口点（ src/main.ts ）：初始化McpServer ，配置传输（ StdioServerTransport ），实例化服务和控制器，并开始监听stdio 。
文件夹结构如下：
src/
├── domain/
│ └── models/ # Domain interfaces
├── infrastructure/
│ └── services/ # External API implementations (Investidor10)
├── application/
│ └── services/ # Business logic and data formatting
├── interface/
│ └── controllers/ # MCP tool registration and validation
└── main.ts # Server entry point
build/ # Compiled JavaScript code
.vscode/ # Contains the mcp.json file, MCP Server configgit clone git@github.com:newerton/mcp-investidor10.git
cd mcp-investidor10
npm install
npm run build按Ctrl+Shift+P并选择“MCP：列出服务器”
选择“股票”，然后选择“启动服务器”
按Ctrl+Shift+P并选择“MCP：列出服务器”
选择“股票”，然后选择“显示输出”
欢迎提交 Pull 请求！欢迎随时提出问题并讨论改进。
该项目根据 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
