Skip to main content
Glama
@gblin-protocol/mcp-server

@gblin-protocol/mcp-server

get_governance_state

Read-onlyIdempotent

Reads GBLIN protocol governance state: vault timelock ownership, minimum delay and grace period, role member counts, pending asset-addition proposal, and optional timelock operation status.

Instructions

Reads GBLIN protocol governance: whether the GBLIN vault is owned by the 48-hour timelock, the timelock's minimum delay and grace period, role member counts, and any pending asset-addition proposal on the vault. With an operation_id it also reports the status of that timelock operation. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_governance_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
operation_idNoOptional 0x-prefixed 32-byte hex id of a specific timelock operation to inspect.

Output Schema

NameRequiredDescriptionDefault
lensNo
ownerYes
vaultYes
timelockYesAddress and minimum delay of the timelock, read on chain.
verificationNo
fee_recipientNo
trust_summaryNo
pending_handoverNoA pending ownership transfer, or null.
owner_is_timelockYes
owner_is_renouncedYes
pending_timelock_operationNoA scheduled timelock operation affecting ownership, or null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.5
    • addedInput schema / required
      Added value: +[]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "fee_recipient": {
      +      "type": "string"
      +    },
      +    "lens": {
      +      "type": "string"
      +    },
      +    "owner": {
      +      "type": "string"
      +    },
      +    "owner_is_renounced": {
      +      "type": "boolean"
      +    },
      +    "owner_is_timelock": {
      +      "type": "boolean"
      +    },
      +    "pending_handover": {
      +      "description": "A pending ownership transfer, or null.",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "pending_timelock_operation": {
      +      "description": "A scheduled timelock operation affecting ownership, or null.",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "timelock": {
      +      "description": "Address and minimum delay of the timelock, read on chain.",
      +      "type": "object"
      +    },
      +    "trust_summary": {
      +      "type": "string"
      +    },
      +    "vault": {
      +      "type": "string"
      +    },
      +    "verification": {
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "vault",
      +    "owner",
      +    "owner_is_timelock",
      +    "owner_is_renounced",
      +    "timelock"
      +  ],
      +  "type": "object"
      +}
  2. First observedv1.1.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered; the description adds useful behavioral detail — the exact governance facets read and that passing operation_id changes the response to include that operation's status. It does not mention permission requirements or freshness/caching, hence not a 5.

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?

Two dense sentences with the core governance read first and the optional operation_id behavior second; nothing is redundant except the trailing 'Read-only', which is minimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 unnecessary; for a zero-required-param, single-optional-param read tool the description covers scope, the optional path, and safety fully.

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 the schema already defines the 0x 32-byte hex format, so baseline would be 3; the description earns a bump by explaining the semantic effect of supplying operation_id (status of that specific timelock operation), which the schema only calls 'inspect'.

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?

Specific verb ('Reads') plus a named resource ('GBLIN protocol governance') followed by an enumeration of what is returned: vault ownership by the timelock, min delay, grace period, role member counts, pending proposals. This clearly separates it from siblings like get_treasury_state or get_auction_state.

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?

It implies usage by describing the content (governance/timelock inspection) and notes the optional operation_id path, but never states when to prefer this over get_treasury_state or the other state tools, and gives no exclusions or prerequisites.

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