Skip to main content
Glama
Sign In
GIA MCP Server

GIA MCP Server

by knowledgepa3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

board_get_session

Read-onlyIdempotent

Retrieve the current status, consensus output, dissenting views, and governance record for a deliberation session. Poll again if status is 'running'.

Instructions

Retrieve the status and output of a governed deliberation session. Returns each seat's position, the synthesized consensus output, dissenting views, and the governance record. If still running, status will be "running" — poll again in 10–15 seconds.

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": {
      "institution_id": "<institution_id>",
      "charter_id": "<charter_id>",
      "session_id": "<session_id>"
    },
    "name": "board_get_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
institution_idYesInstitution ID
charter_idYesCharter ID
session_idYesSession ID from board_convene_session

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.6

TDQS

A4.3/5.0
Behavior4/5

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

Despite annotations already indicating readOnlyHint=true and idempotentHint=true, the description adds valuable behavioral details: what is returned (seat positions, consensus, dissenting views, governance record) and polling behavior. No contradictions.

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?

The description is two sentences, front-loaded with the core purpose, and every sentence adds value. No wasted words.

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?

Given the tool's three required parameters and no output schema, the description explains both the return fields and the polling behavior for running sessions. This is complete for a read-only retrieval 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?

Input schema has 100% coverage with clear descriptions for each parameter. The tool description does not add additional meaning beyond what the schema provides, meeting the baseline expectation.

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?

The description explicitly states 'Retrieve the status and output of a governed deliberation session', using a specific verb and resource. It clearly distinguishes from sibling tools like board_convene_session, which creates sessions.

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 description provides context on when to use the tool (after convening a session) and includes polling advice for running sessions. It does not explicitly state when not to use it, but the guidance is clear and actionable.

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

Deploy Server

Other Tools