Skip to main content
Glama

Last Price

use_api_key

Idempotent

Use a Last Price API key you already hold (a saved file, LASTPRICE_API_KEY) in this MCP connection, when it was opened without one: pass api_key. On the hosted MCP server this session then runs as that key's agent, so the tools that need a credential work at once with no header to add; it lasts until the session ends or the key is revoked or rotated. The key is checked, never echoed back. A connection that already has a credential keeps it. Public: needs no other credential.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "api_key": "<api_key>"
    },
    "name": "use_api_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyYesYour Last Price API key: lp_ and 40 lowercase hex characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. Added
  12. Removed
  13. Added
  14. Removed
  15. Added
  16. Removed
  17. Added
  18. Removed
  19. Added
  20. Removed
  21. Added
  22. Removed
  23. Added
  24. Removed
  25. Added
  26. Removed
  27. Added
  28. Removed
  29. Added
  30. Removed
  31. Added
  32. Removed
  33. Added
  34. Removed
  35. Added
  36. Removed
  37. Added
  38. Removed
  39. Added
  40. Removed
  41. Added
  42. Removed
  43. Added
  44. Removed
  45. Added
  46. Removed
  47. Added
  48. Removed
  49. Added
  50. Removed
  51. Added
  52. Removed
  53. Added
  54. Removed
  55. Added
  56. Removed
  57. Added
  58. Removed
  59. Added
  60. Removed
  61. Added
  62. Removed
  63. Added
  64. Removed
  65. Added
  66. Removed
  67. Added
  68. Removed
  69. Added
  70. Removed
  71. Added
  72. Removed
  73. Added
  74. Removed
  75. Added
  76. Removed
  77. Added
  78. Removed
  79. Added
  80. Removed
  81. Added
  82. Removed
  83. Added
  84. Removed
  85. Added
  86. Removed
  87. Added
  88. Removed
  89. Added
  90. Removed
  91. Added
  92. Removed
  93. Added
  94. Removed
  95. Added
  96. Removed
  97. Added
  98. Removed
  99. Added
  100. Removed
  101. Added
  102. Removed
  103. Added
  104. Removed
  105. Added
  106. Removed
  107. Added
  108. Removed
  109. Added
  110. Removed
  111. Added
  112. Removed
  113. Added
  114. Removed
  115. Added
  116. Removed
  117. Added
  118. Removed
  119. Added
  120. Removed
  121. Added
  122. Removed
  123. Added
  124. Removed
  125. Added
  126. Removed
  127. Added
  128. Removed
  129. Added
  130. Removed
  131. Added
  132. Removed
  133. Added
  134. Removed
  135. Added
  136. Removed
  137. Added
  138. Removed
  139. Added
  140. Removed
  141. Added

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations: discloses that the key becomes the session's identity, that the effect is session-scoped and ends on session end/revocation/rotation, that the key is validated but never echoed, and that existing credentials take precedence. That is exactly the lifecycle and side-effect information an agent needs for a stateful auth operation with destructiveHint=false but readOnlyHint=false.

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?

Compact and front-loaded — the precondition and the action come first, then consequences, then the security note. The first sentence is an awkward colon-spliced run-on, but no sentence is filler.

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 single required parameter with full schema coverage and no output schema, the description covers scope, duration, and credential precedence, which is what an agent needs to decide and act. It does not say what happens on an invalid or revoked key at call time, a minor gap given the schema pattern already screens format.

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?

Schema coverage is 100% and already specifies the lp_ + 40-hex pattern, so the baseline is 3. The description adds real value by telling the agent where the value comes from (a saved file or LASTPRICE_API_KEY env var the caller already holds), which the schema does not say.

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?

States a specific action — authenticating the current MCP session with a Last Price API key the caller already holds — and names the concrete condition (connection was opened without one). No sibling tool in the list does anything comparable, so there is no ambiguity to resolve.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives both the trigger (session opened without a credential) and the exclusion (a connection that already has a credential keeps it, so this call is unnecessary). It also notes the endpoint is public and needs no other credential, removing a common precondition question.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources