Skip to content

Commit b2f147c

Browse files
Hyperlint Automation Fix
1 parent 02a2919 commit b2f147c

File tree

1 file changed

+1
-1
lines changed
  • src/content/docs/agents/model-context-protocol

1 file changed

+1
-1
lines changed

src/content/docs/agents/model-context-protocol/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ The MCP standard supports two modes of operation:
3030
- **Tool design**: Don’t treat your MCP server as a wrapper around your full API schema. Instead, build tools that are optimized for specific user goals and reliable outcomes. Fewer, well-designed tools often outperform many granular ones, especially for agents with small context windows or tight latency budgets.
3131
- **Scoped permissions**: Deploying several focused MCP servers, each with narrowly scoped permissions, reduces the risk of over-privileged access and makes it easier to manage and audit what each server is allowed to do.
3232
- **Tool descriptions**: Detailed parameter descriptions help agents understand how to use your tools correctly — including what values are expected, how they affect behavior, and any important constraints. This reduces errors and improves reliability.
33-
- **Evaluation tests**: Use evaluation tests (evals) to measure the agent’s ability to use your tools correctly. Run these after any updates to your server or tool descriptions to catch regressions early and track improvements over time.
33+
- **Evaluation tests**: Use evaluation tests ('evals') to measure the agent’s ability to use your tools correctly. Run these after any updates to your server or tool descriptions to catch regressions early and track improvements over time.
3434

3535
### Get Started
3636

0 commit comments

Comments
 (0)