P-Link-MCP

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.0.0
Disambiguation4/5
Most tools have distinct purposes, such as funding, transaction retrieval, wallet management, and payments. However, get_wallet_and_otp combines wallet creation and OTP retrieval, which could cause confusion with login_with_otp, leading to minor ambiguity in their overlapping OTP-related functions.
Naming Consistency3/5
The naming is mixed with some consistency in verb_noun patterns like get_transaction_state and get_wallet_history, but deviations exist such as fund_my_wallet (verb_pronoun_noun), pay_and_get_402_protected_url (complex compound), and ping (single word). This creates a readable but inconsistent convention overall.
Tool Count5/5
With 11 tools, the count is well-scoped for a P-Link wallet and payment management server. Each tool serves a clear function in handling wallets, transactions, payments, and server health, making the set comprehensive without being overwhelming.
Completeness4/5
The tool set covers key operations like wallet creation, funding, transaction history, payments, and authentication, supporting core workflows. A minor gap is the lack of tools for updating wallet details or managing tokens beyond basic retrieval, but agents can work around this with the existing tools.
Average 2.8/5 across 11 of 11 tools scored. Lowest: 2.2/5.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 0 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
This repository is licensed under Apache 2.0.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate readOnlyHint=true, suggesting a safe read operation, which aligns with the description's 'get' action. However, the description adds minimal context beyond this—it doesn't disclose security implications (e.g., private keys are sensitive), rate limits, or what the output entails (e.g., plaintext key, encrypted data). With annotations covering basic safety, it earns a baseline score but lacks depth.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that repeats the name/title, making it under-specified rather than concise. It wastes space on redundant information (e.g., the URL) without adding useful context. A more effective description would front-load critical details like security warnings or usage context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool handling sensitive private keys with no output schema and minimal annotations, the description is inadequate. It doesn't explain return values (e.g., key format, encryption), error conditions, or security risks. Given the high-stakes nature of private key access, more completeness is needed to guide safe usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, with the parameter 'solanaWalletAddress' clearly documented. The description doesn't add any parameter-specific details (e.g., why this address is needed, format constraints beyond the schema). Since the schema does the heavy lifting, the baseline score of 3 is appropriate, but no extra value is provided.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tautological: description restates name/title.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication, wallet setup), use cases (e.g., backup, recovery), or exclusions (e.g., not for public wallets). Given siblings like 'get_wallet_info', the description fails to clarify why one would choose this tool over others.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations provide readOnlyHint=true, indicating this is a safe read operation. The description adds minimal behavioral context by suggesting two possible outcomes (create wallet or get OTP), but doesn't explain conditions triggering each outcome, whether this is idempotent, or what happens if a wallet already exists. It doesn't contradict annotations, but adds only basic value beyond them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
While technically concise with a single sentence, the description is under-specified rather than efficiently structured. It repeats the title verbatim without adding explanatory value, failing to front-load critical information about the tool's dual functionality or usage context. The brevity comes at the cost of clarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with ambiguous dual functionality (create wallet OR get OTP), no output schema, and multiple sibling tools, the description is inadequate. It doesn't explain the relationship between the two operations, expected return values, error conditions, or how this integrates with the broader wallet system. The annotations provide basic safety information but don't compensate for the description's lack of completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with the email parameter fully documented in the schema. The description adds no parameter-specific information beyond what's already in the schema (e.g., no clarification on email format requirements or how it's used differently for wallet creation versus OTP retrieval). Baseline 3 is appropriate when the schema carries the full parameter documentation burden.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tautological: description restates name/title.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
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. There's no mention of prerequisites, when to choose this over 'fund_my_wallet' or 'login_with_otp', or whether this is for initial setup versus ongoing authentication. The agent receives no usage context beyond the ambiguous dual-purpose statement.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description does not disclose behavioral traits beyond what annotations provide. Annotations indicate readOnlyHint=true, implying a safe read operation, which the description aligns with by using 'retrieve'. However, it adds no additional context such as rate limits, authentication needs, or data freshness, relying solely on annotations for behavioral insight.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that repeats the title verbatim, adding no new information. This is inefficient and under-specified, failing to earn its place with meaningful content, though it is not overly verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has annotations (readOnlyHint) and a well-documented input schema but no output schema, the description is minimally complete. It covers the basic purpose but lacks details on return values, error handling, or integration with sibling tools, making it adequate but with clear gaps for an agent to understand full context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds no meaning beyond the input schema, which has 100% coverage for the single parameter 'pubk'. The schema already describes it as an optional Solana address defaulting to the connected wallet. With high schema coverage, the baseline score of 3 is appropriate, as the description does not compensate with extra parameter details.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tautological: description restates name/title.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
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. For example, it does not clarify if this is for general wallet info versus more specific tools like 'get_wallet_history' for transaction history or 'get_private_key_of_wallet' for sensitive data, leaving the agent without explicit usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate readOnlyHint=true, suggesting a safe operation, but the description doesn't add behavioral context beyond this. It doesn't disclose what happens upon login (e.g., session creation, token return, error handling) or any rate limits. With annotations covering safety, the description adds minimal value, earning a baseline score for not contradicting them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is repetitive, echoing the title without adding value, making it inefficient. It consists of two redundant sentences that don't earn their place. While brief, it's under-specified rather than concise, failing to front-load useful information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For an authentication tool with no output schema and minimal annotations, the description is inadequate. It doesn't explain what happens after login (e.g., returns a session token, grants access to other tools) or error conditions. Given the complexity of authentication and lack of output details, more completeness is needed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with clear documentation for both parameters (email and otp). The description doesn't add any meaningful semantics beyond what the schema provides, such as format details or usage tips. Given high schema coverage, a baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tautological: description restates name/title.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives is provided. While it mentions receiving OTP via email, it doesn't clarify prerequisites (e.g., must have an account, OTP must be valid) or contrast with other authentication methods. The context is implied but lacks explicit when/when-not instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, indicating no state change, but the description claims 'create' which implies a write operation—this is a contradiction. However, the description adds value by specifying payment methods (credit card/Solana tokens with auto-conversion to USDC), which isn't covered by annotations. It lacks details on link lifespan, security, or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, repetitive sentence that restates the title verbatim without adding new information or structuring details. It wastes space by not front-loading key insights or expanding on usage, making it inefficient despite its brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with 11 parameters, no output schema, and annotations that only cover read-only status, the description is inadequate. It fails to explain return values (e.g., link format), error conditions, or behavioral nuances like webhook triggers, leaving significant gaps for agent invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so parameters are fully documented in the schema. The description doesn't add any parameter-specific details beyond what's in the schema (e.g., it doesn't explain 'receivingPayment' formats or 'param' usage). Baseline 3 is appropriate as the schema carries the burden, but no extra semantic context is provided.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tautological: description restates name/title.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
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 like 'send_money' (for active payments) or 'fund_my_wallet' (for direct funding). It mentions payment methods (credit card/Solana) but doesn't specify use cases, prerequisites, or exclusions, leaving the agent to infer usage from the purpose alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations include readOnlyHint=true, indicating this is a safe read operation. The description adds no behavioral traits beyond this, such as rate limits, authentication needs, or what 'state and details' entail (e.g., confirmation status, metadata). However, it does not contradict annotations, so it meets the lower bar with annotations present but adds minimal context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the core action. However, it lacks structure (e.g., no separation of purpose from usage) and is overly brief, missing opportunities to add value without verbosity. It earns a 4 for zero waste but loses points for under-specification in a tool-rich context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given one parameter with full schema coverage and readOnlyHint annotation, the description is minimally adequate. However, with no output schema and siblings like 'get_wallet_history', it should clarify return values (e.g., transaction status, timestamps) and differentiate from other tools. It meets basic needs but leaves gaps in a complex server environment.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with the parameter 'trxID' documented as 'The transaction ID'. The description adds no meaning beyond this, such as format examples (e.g., base58 string) or validation rules. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but doesn't need to heavily.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tautological: description restates name/title.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. Given siblings like 'get_wallet_history' (which might list transactions) and 'send_money' (which might create transactions), the description offers no context about use cases, prerequisites, or exclusions. It merely states what the tool does without addressing when it's appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, indicating this is a safe read operation. The description adds useful context about what's retrieved ('received and sent funds with dates'), but doesn't disclose behavioral traits like pagination, rate limits, or authentication requirements beyond what's implied by the parameter description. No contradiction with annotations exists.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the core purpose. However, it repeats the title verbatim without adding extra value, slightly reducing its effectiveness, but it remains appropriately sized with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity (retrieving transaction history), lack of output schema, and rich annotations (readOnlyHint), the description is adequate but incomplete. It covers what the tool does but doesn't address return format, error handling, or prerequisites, leaving gaps for the agent to infer.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with the single parameter 'walletAddress' fully documented in the schema. The description doesn't add any parameter-specific details beyond what the schema provides, such as format requirements or examples, 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.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tautological: description restates name/title.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
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. It doesn't mention sibling tools like 'get_transaction_state' (which might retrieve a single transaction) or 'get_wallet_info' (which might provide wallet metadata rather than transaction history), leaving the agent with no explicit usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations include readOnlyHint=true, indicating this is a read operation. The description adds context by explaining that it 'obtains a link' or provides a 'Solana address', which clarifies the tool's behavior beyond just reading data. However, it doesn't detail rate limits, authentication needs, or what the link/address is used for, leaving some behavioral aspects unclear.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that repeats the title verbatim, which is redundant and not front-loaded with unique value. While it's concise, it wastes space by not adding new information beyond the title, reducing its effectiveness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (funding operations), lack of output schema, and minimal annotations, the description is somewhat incomplete. It covers the purpose and methods but doesn't explain return values, error conditions, or integration details. With no output schema, more context on what to expect would be beneficial.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 1 parameter with 100% description coverage, clearly documenting 'amount' as 'Amount to fund in your wallet in USD'. The description doesn't add any parameter-specific information beyond what the schema provides, such as format details or constraints. With high schema coverage, the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tautological: description restates name/title.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when funding a wallet via credit card or Solana, but doesn't provide explicit guidance on when to use this tool versus alternatives like 'request_payment_link' or 'send_money'. It mentions two methods but doesn't specify prerequisites or exclusions, leaving the context somewhat vague.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate destructiveHint=true and openWorldHint=true, which already inform the agent that this is a mutating operation with potentially open-ended outcomes. The description adds context by specifying the payment mechanism ('P-Link managed account') and that it 'returns the result,' but doesn't elaborate on what the result includes (e.g., success/failure, transaction details) or behavioral traits like rate limits, authentication needs, or error handling. No contradiction with annotations exists.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the core action: 'Pay a HTTP 402 protected URL using your P-Link managed account, and returns the result.' It has zero waste, directly mirroring the title and name without redundancy, making it highly concise and well-structured for quick understanding.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (a payment operation with destructive and open-world hints), the description is minimally complete. It clarifies the purpose and mechanism but lacks details on output (no output schema provided), error cases, or integration with sibling tools. While annotations cover safety aspects, the description could better address the agent's need to understand what 'returns the result' entails in practice.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, with the 'url' parameter documented as 'The 402 protected URL (can be any link complying to the x402 protocol).' The description doesn't add any meaning beyond this, such as examples or constraints on URL format. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't need to.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tautological: description restates name/title.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
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. It doesn't mention prerequisites (e.g., having a funded wallet), exclusions (e.g., non-402 URLs), or comparisons to siblings like 'request_payment_link' (which might create payment links) or 'send_money' (which might handle direct transfers). Usage is implied only by the tool's name and purpose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations provide destructiveHint=true and openWorldHint=true, indicating a write operation with potential side effects. The description adds valuable behavioral context beyond annotations: it explains the claim mechanism for new users, the 3-day timeout, and automatic return of funds if unclaimed. This clarifies the tool's operational behavior without contradicting annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the core action and follows with critical behavioral details. Every part earns its place: the main purpose, recipient options, claim mechanism, and timeout policy are all essential without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a destructive tool with no output schema, the description provides good context: it covers the action, recipient types, claim process, and timeout behavior. However, it doesn't mention error conditions, authentication requirements, or what happens after sending (e.g., confirmation details), leaving some gaps in operational completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 100% schema description coverage, the input schema already documents all parameters thoroughly (to, amount, currency, title). The description doesn't add any parameter-specific details beyond what's in the schema, such as format examples or usage nuances. Baseline 3 is appropriate since the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tautological: description restates name/title.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implicitly provides usage context by specifying recipient types (email, Solana wallet, phone) and mentioning a 3-day claim period, which helps determine when to use it. However, it lacks explicit guidance on when to choose this tool over alternatives like 'pay_and_get_402_protected_url' or 'request_payment_link', and doesn't mention prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the return value ({ result: 'OK' }) and the condition for that return ('if the server is alive'), which are useful behavioral traits. However, it lacks details on error handling, latency, or other operational aspects that might be relevant for a health check tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with the core purpose in the first sentence and adds return details in the second. Both sentences earn their place by providing essential information without redundancy, making it appropriately sized and efficient for a simple tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's low complexity (1 optional parameter, no output schema, no annotations), the description is reasonably complete. It explains what the tool does and what it returns, which covers the basics. However, it could be more complete by addressing the optional parameter or potential error cases, but this is a minor gap for such a straightforward tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 1 parameter with 0% description coverage, and the description does not mention the 'msg' parameter at all. Since there are 0 required parameters, the baseline is 4, as the tool can be used without parameters. The description's focus on the return value compensates somewhat for the lack of param info, but does not fully address the undocumented parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with specific verbs ('health check') and resource ('MCP server'), and it distinguishes from siblings by focusing on server status rather than wallet/transaction operations. It explicitly mentions what it returns, making the purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage context ('if the server is alive') for checking server health, but does not explicitly state when to use this vs. alternatives or provide exclusions. Given the simple nature of this tool and its clear purpose, the implied guidance is sufficient for most cases, though not exhaustive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![P-Link-MCP MCP server](https://glama.ai/mcp/servers/paracetamol951/P-Link-MCP/badges/card.svg)](https://glama.ai/mcp/servers/paracetamol951/P-Link-MCP)

Score Badge

Copy to your README.md:

[![P-Link-MCP MCP server](https://glama.ai/mcp/servers/paracetamol951/P-Link-MCP/badges/score.svg)](https://glama.ai/mcp/servers/paracetamol951/P-Link-MCP)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/paracetamol951/P-Link-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server