agentmako

Overview Schema Related Servers Score Discussions

db_rpc

db_rpc

Read-onlyIdempotent

Inspect stored procedures and functions: view signatures, return shapes, languages, and security settings by name or list routines with detailed metadata.

Instructions

Read-only database tool for function questions: inspect one stored procedure/function signature by name, or pass list: true to enumerate routines with signatures, return shape, language, and security.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`list`	No
`name`	No
`limit`	No
`schema`	No
`argTypes`	No
`projectId`	No
`projectRef`	No
`includeSource`	No
`includeSystemSchemas`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`args`	No
`mode`	No
`name`	No
`rpcs`	No
`limit`	No
`_hints`	Yes
`schema`	No
`source`	No
`returns`	No
`language`	No
`toolName`	Yes
`truncated`	No
`volatility`	No
`totalReturned`	No
`securityDefiner`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed10 schema fields changedv0.4.0Jun 28, 2026

addedInput schema / properties / includeSystemSchemas
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / limit

Added value: +{
+  "maximum": 1000,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / list
```
Added value: +{
+  "type": "boolean"
+}
```
removedInput schema / required
```
Removed value: -[
-  "name"
-]
```

addedOutput schema / properties / limit

Added value: +{
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / mode

Added value: +{
+  "enum": [
+    "lookup",
+    "list"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / rpcs

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "argTypes": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "args": {
+        "items": {
+          "$ref": "#/properties/args/items"
+        },
+        "type": "array"
+      },
+      "kind": {
+        "enum": [
+          "function",
+          "procedure"
+        ],
+        "type": "string"
+      },
+      "language": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "returns": {
+        "type": "string"
+      },
+      "schema": {
+        "type": "string"
+      },
+      "securityDefiner": {
+        "type": "boolean"
+      },
+      "volatility": {
+        "enum": [
+          "immutable",
+          "stable",
+          "volatile"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "schema",
+      "kind",
+      "argTypes",
+      "args",
+      "returns",
+      "language",
+      "securityDefiner",
+      "volatility"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / totalReturned

Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / truncated
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "toolName",
-  "name",
-  "schema",
-  "args",
-  "returns",
-  "language",
-  "securityDefiner",
-  "volatility",
-  "source",
-  "_hints"
-]New value: +[
+  "toolName",
+  "_hints"
+]

Addedv0.2.5Apr 30, 2026
Removedv0.2.4Apr 30, 2026
First observedv0.2.3Apr 29, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Description states read-only, matching annotations, and adds that it returns signatures, return shape, language, and security, which goes beyond annotation hints. It also describes two modes of operation.

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?

Single sentence is concise and front-loaded with the core purpose. No waste, though could benefit from clearer separation of modes.

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?

Covers main usage modes and mentions return shape, language, security, but lacks explanation of many parameters. Output schema exists but not detailed. Adequate but with gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only 'name' and 'list' are explained in the description, leaving 7 other parameters (e.g., limit, schema, argTypes) completely undocumented. With 0% schema description coverage, this is insufficient.

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?

Description explicitly states the tool inspects stored procedure/function signatures or enumerates routines, with specific verb 'inspect' and 'enumerate'. This clearly distinguishes it from siblings like rpc_neighborhood and trace_rpc.

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?

Clearly implies usage for function questions (inspecting signatures or listing routines), but does not explicitly exclude other cases or mention alternatives. Context is clear enough for an agent.

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

Install Server

Other Tools

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/drhalto/agentmako'

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