Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds concrete behavioral detail: it returns authenticated:true and empty pending[] when all providers are connected, and connect_url plus per‑install URLs when credentials are missing. This goes beyond the annotations and helps predict the tool's output without any contradiction.
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, front‑loaded sentence that immediately states the function and then provides two concrete outcome scenarios. No unnecessary words; every clause adds value.
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?
Even without an output schema, the description fully explains the return shape and behavior for both the success case and the missing‑credentials case. For a simple status tool, this is complete and self‑contained.
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 tool takes zero parameters and the schema is empty (100% coverage). With no parameters to document, the description naturally needs no parameter explanation, earning the baseline of 4 for parameter semantics.
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 starts with 'Returns connection status and URLs,' which is a specific verb+resource. It distinguishes itself from siblings like 'authenticate' and 'marketplace' by focusing on status checking, making its purpose unmistakable.
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 context for when to use is clear: check connection status. It explains outcomes for connected vs. missing credentials but does not explicitly name alternatives or exclusions. Given sibling names, it's evidently the go‑to for status queries, though it could have been more direct about 'use this when you need connection state.'
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
marketplace and search_tools both provide search/describe/invoke over the MCP catalog, so an agent can easily pick the wrong one. authenticate and connect also overlap somewhat on auth/status concerns, though less severely.
Names mix bare verbs (authenticate, connect), a noun (marketplace), and compound forms (report_bug, search_tools, show_version, toolkit_info). They are readable and mostly action-oriented, but there is no single predictable convention.
Seven tools is within a reasonable raw range, but the count is less appropriate than it appears because marketplace is a mega-tool with many suboperations and search_tools duplicates its core functionality. The set could be leaner and better structured.
For the inferred MCP-platform-management domain, auth, status, catalog search/invoke, bug reporting, version, and toolkit info are covered. However, the server is named Stripe, and no payment or Stripe-specific API tools exist, making the surface severely incomplete for the apparent purpose.