Skip to main content
Glama

us-lobbying-mcp-server

Describe disclosure tables

uslobbying_dataframe_describe
Read-onlyIdempotent

Inspect exact staged table schemas, row counts, lifecycle, acquisition coverage and provenance before SQL.

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": {
      "canvas_id": "<canvas_id>"
    },
    "name": "uslobbying_dataframe_describe"
  }
}

Input Schema

NameRequiredDescriptionDefault
canvas_idYesCanvas token returned by an analytical disclosure tool.
table_nameNoExisting table to inspect; omit for every table in this canvas.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
tablesNoComplete table metadata, or an empty array for an empty canvas.
guidanceNoTable names and dataframe instructions.
canvas_idNoTenant-scoped canvas access token.
query_toolNoQuery or retrieve materialized table rows.
describe_toolNoInspect exact table schemas before SQL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `query_row_too_large`: Complete table metadata exceeds the result byte budget. `canvas_unavailable`: Canvas is not configured. `canvas_not_found`: Canvas token is unknown or expired. `missing_table`: Named table is absent or expired. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `canvas_unavailable`: Canvas is not configured. `canvas_not_found`: Canvas token is unknown or expired. `missing_table`: Named table is absent or expired. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "query_row_too_large",
      -  "canvas_unavailable",
      -  "canvas_not_found",
      -  "missing_table"
      -]New value: +[
      +  "canvas_unavailable",
      +  "canvas_not_found",
      +  "missing_table"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent and closed-world behavior, so the safety profile is covered. The description adds value by listing what is inspected (lifecycle, acquisition coverage, provenance) beyond what annotations convey. It says nothing about cost, whether inspection is expensive on wide canvases, or any limits when omitting table_name to scan every table.

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?

A single dense sentence with the action front-loaded and no filler; every listed noun maps to something the tool actually reports.

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?

With an output schema covering return values, 100% parameter documentation, and annotations covering safety, the description needs only to state purpose and placement — which it does. Only marginal gaps remain (no mention of what happens with invalid or unstaged table names).

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 description coverage is 100% — canvas_id and table_name are both fully documented in the schema, including the omit-to-list-all behavior. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Inspect') and resource ('staged table schemas') and enumerates the dimensions returned (row counts, lifecycle, acquisition coverage, provenance), so an agent knows exactly what this tool produces. It doesn't name a sibling tool outright, but 'before SQL' implicitly separates it from uslobbying_dataframe_query.

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?

'before SQL' gives a clear temporal placement in the workflow — call this ahead of querying — which is genuine usage guidance. There is no explicit when-not, no named alternative, and no stated prerequisit (e.g., that a canvas must already contain stagged tables).

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.