Skip to main content
Glama

Zebu Data - YouTube Data & Transcripts

Get key-value store record

get-key-value-store-record
Read-onlyIdempotent

Get the value stored under a specific key in a key-value store — a single record, not a listing of all keys. Requires the exact key name. The response preserves the original Content-Encoding; most clients handle decompression automatically. A record over 262144 bytes is returned as a link to download it, not as its value.

USAGE:

  • Use when you need to retrieve a specific record (JSON, text, or binary) from a store.

USAGE EXAMPLES:

  • user_input: Get record INPUT from store abc123

  • user_input: Get record data.json from store username~my-store

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": {
      "keyValueStoreId": "<keyValueStoreId>",
      "recordKey": "<recordKey>"
    },
    "name": "get-key-value-store-record"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordKeyYesKey of the record to retrieve.
keyValueStoreIdYesKey-value store ID, name (resolved against your own key-value stores), or full name as username~name.

Output Schema

NameRequiredDescriptionDefault
keyYesRecord key
valueYesThe stored value (JSON, text, or binary)
summaryYesSummary of the result
contentTypeNoMIME type of the stored value
keyValueStoreIdYesKey-value store ID

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
  142. Removed
  143. Added
  144. Removed
  145. Added
  146. Removed
  147. Added
  148. Removed
  149. Added
  150. Removed
  151. Added
  152. Removed
  153. Added
  154. Removed
  155. Added
  156. Removed
  157. Added
  158. Removed
  159. Added
  160. Removed
  161. Added
  162. Removed
  163. Added
  164. Removed
  165. Added
  166. Removed
  167. Added
  168. Removed
  169. Added
  170. Removed
  171. Added
  172. Removed
  173. Added
  174. Removed
  175. Added
  176. Removed
  177. Added
  178. Removed
  179. Added
  180. Removed
  181. Added
  182. Removed
  183. Added
  184. Removed
  185. Added
  186. Removed
  187. Added
  188. Removed
  189. Added
  190. Removed
  191. Added
  192. Removed
  193. Added
  194. Removed
  195. Added
  196. Removed
  197. Added
  198. Removed
  199. Added
  200. Removed
  201. Added
  202. Removed
  203. Added
  204. Removed
  205. Added
  206. Removed
  207. Added
  208. Removed
  209. Added
  210. Removed
  211. Added
  212. Removed
  213. Added
  214. Removed
  215. Added
  216. Removed
  217. Added
  218. Removed
  219. Added
  220. Removed
  221. Added
  222. Removed
  223. Added
  224. Removed
  225. Added
  226. Removed
  227. Added
  228. Removed
  229. Added
  230. Removed
  231. Added
  232. Removed
  233. Added
  234. Removed
  235. Added
  236. Removed
  237. Added
  238. Removed
  239. Added
  240. Removed
  241. Added
  242. Removed
  243. Added
  244. Removed
  245. Added
  246. Removed
  247. Added
  248. Removed
  249. Added
  250. Removed
  251. Added
  252. Removed
  253. Added
  254. Removed
  255. Added
  256. Removed
  257. Added
  258. Removed
  259. Added
  260. Removed
  261. Added
  262. Removed
  263. Added
  264. Removed
  265. Added
  266. Removed
  267. Added
  268. Removed
  269. Added
  270. Removed
  271. Added
  272. Removed
  273. Added
  274. Removed
  275. Added
  276. Removed
  277. Added
  278. Removed
  279. Added
  280. Removed
  281. Added
  282. Removed
  283. Added
  284. Removed
  285. Added
  286. Removed
  287. Added
  288. Removed
  289. Added
  290. Removed
  291. Added
  292. Removed
  293. Added
  294. Removed
  295. Added
  296. Removed
  297. Added
  298. Removed
  299. Added
  300. Removed
  301. Added
  302. Removed
  303. Added
  304. Removed
  305. Added
  306. Removed
  307. Added
  308. Removed
  309. Added
  310. Removed
  311. Added
  312. Removed
  313. Added
  314. Removed
  315. Added
  316. Removed
  317. Added
  318. Removed
  319. Added
  320. Removed
  321. Added
  322. Removed
  323. Added
  324. Removed
  325. Added
  326. Removed
  327. Added
  328. Removed
  329. Added
  330. Removed
  331. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely non-obvious behavior: the response preserves the original Content-Encoding, and records over 262144 bytes come back as a download link rather than the value. It does not say what happens when the key is absent, which is the main remaining behavioral unknown.

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?

Front-loaded with the core statement, then scoped behavior, then usage and two short examples. Every line carries information an agent needs, and there is no redundant restatement of the title or annotations.

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?

An output schema exists so return-value explanation is not required, and annotations carry the safety profile, leaving the description to cover the two unusual behaviors it does cover (encoding preservation, size-based link response). The only omission is error behavior for a missing or malformed key, which is minor for a read-only two-parameter tool.

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 coverage is 100% and both properties already document the key and the accepted store-ID forms (ID, name, username~name), so the description only reinforces 'requires the exact key name' and echoes the username~my-store form in an example. That is marginal added meaning over a fully documented schema, matching the baseline 3.

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?

Names a specific verb and resource ('get the value stored under a specific key in a key-value store') and explicitly bounds the scope ('a single record, not a listing of all keys'), so the agent can distinguish it from any list-style sibling without opening the schema.

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 USAGE block gives an explicit condition ('when you need to retrieve a specific record (JSON, text, or binary) from a store') and two concrete example inputs. It lacks an explicit when-not or a named alternative tool, though no listed sibling performs a comparable retrieval, so the practical gap is small.

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.