Hiring Signals

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

Name	Required	Description	Default
`recordKey`	Yes	Key of the record to retrieve.
`keyValueStoreId`	Yes	Key-value store ID, name (resolved against your own key-value stores), or full name as username~name.

Output Schema

Name	Required	Description
`key`	Yes	Record key
`value`	Yes	The stored value (JSON, text, or binary)
`summary`	Yes	Summary of the result
`contentType`	No	MIME type of the stored value
`keyValueStoreId`	Yes	Key-value store ID

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 13, 2026
- addedInput schema / properties / keyValueStoreId / maxLength
```
Added value: +256
```
- addedInput schema / properties / recordKey / maxLength
```
Added value: +256
```

Changed1 schema field changedOct 29, 2026

changedInput schema / properties / keyValueStoreId / description

Previous value: -"Key-value store ID or username~store-name."New value: +"Key-value store ID, name (resolved against your own key-value stores), or full name as username~name."

Changed1 schema field changedOct 15, 2026

addedOutput schema / properties / value / anyOf

Added value: +[
+  {
+    "type": "object"
+  },
+  {
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

First observedOct 5, 2026

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.

All Hiring Signals tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.