get_account_linksLinks to create an account, sign in and manage connections.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| mcp | Yes | ||
| links | Yes | ||
| disclosureUnits | Yes | ||
| mcpAvailability | Yes | Public availability follows release controls. Plan MCP capabilities may be listed before public availability. | |
| availabilityMessage | Yes | ||
| browserConfirmationRequired | Yes |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": false,
+ "description": "MCP get_account_links result: official links for account creation, sign-in, account management and comparing plans, with a pointer to kunkafa.com.",
+ "properties": {
+ "availabilityMessage": {
+ "type": "string"
+ },
+ "browserConfirmationRequired": {
+ "const": true
+ },
+ "disclosureUnits": {
+ "const": 0
+ },
+ "links": {
+ "additionalProperties": false,
+ "properties": {
+ "documentation": {
+ "pattern": "^https://kunkafa\\.com/",
+ "type": "string"
+ },
+ "manage": {
+ "pattern": "^https://kunkafa\\.com/",
+ "type": "string"
+ },
+ "signin": {
+ "pattern": "^https://kunkafa\\.com/",
+ "type": "string"
+ },
+ "signup": {
+ "pattern": "^https://kunkafa\\.com/",
+ "type": "string"
+ }
+ },
+ "required": [
+ "signup",
+ "signin",
+ "manage",
+ "documentation"
+ ],
+ "type": "object"
+ },
+ "mcp": {
+ "const": "https://kunkafa.com/mcp"
+ },
+ "mcpAvailability": {
+ "description": "Public availability follows release controls. Plan MCP capabilities may be listed before public availability.",
+ "enum": [
+ "coming_soon",
+ "available"
+ ]
+ }
+ },
+ "required": [
+ "mcp",
+ "links",
+ "browserConfirmationRequired",
+ "disclosureUnits",
+ "mcpAvailability",
+ "availabilityMessage"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the output is links for account actions, but does not disclose auth requirements, rate limits, or other behavioral traits beyond the annotations.
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 sentence, front-loaded with the resource and its uses. It is appropriately sized and has no filler, though it could be slightly more informative without becoming verbose.
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?
Given the low complexity (no parameters), the presence of an output schema, and rich annotations, the description is mostly complete for an agent to call the tool correctly. It does not explain when to use it relative to siblings, but those siblings are unrelated utilities.
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 schema coverage is 100%. With no parameters to document, the baseline is 4; the description neither adds nor detracts from 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 states a specific resource (links) and their intended purposes: creating an account, signing in, and managing connections. This is clear and distinguishes it from unrelated siblings like follow_market or get_glossary, though it does not explicitly contrast with any alternative.
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?
Usage is implied by the listed purposes (account creation, sign-in, connection management), but there is no explicit when-to-use, when-not-to-use, or alternative tool guidance. Adequate for a simple no-param tool but leaves selection criteria to inference.
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.