We rewrote all 50 of our MCP tool descriptions to get into Claude's Connectors Directory
I build LastPing , a monitoring service for cron jobs, CI pipelines and AI agents. It has a remote MCP server with 50 tools, so an agent can create monitors, read failed runs and write notes on incidents. This week it was listed in Claude's Connectors Directory. Getting there meant rewriting every tool description we had. If you run an MCP server, the lesson applies to you whether or not you ever…
LastPing is a monitoring service that tracks cron jobs, CI pipelines and AI agents. To get listed in Claude's Connectors Directory, it was necessary to rewrite every tool description for the service's 50 MCP tools. The rewrite focused on removing any instructions that directed the model to behave in certain ways or use other tools.
The new descriptions simply stated what the tool does and when it should be used, avoiding any imperatives, hidden instructions or other model behavior. The result was descriptions that were concise, honest about tool functionality, and did not push the model into taking unnecessary actions. The change proved effective, with agents continuing to function correctly after the rewrite.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
