GetSign MCP

getsign_account

Read-onlyIdempotent

Check GetSign auth and Monday-app install state.

    action=preflight (default): token configured + GET /account if connected.
    action=status: whether a session token is configured (does not probe /account).
    action=install_state: whether the Monday app is installed (tri-state). Pass
    account_id for an account that has never connected — defaults to this session.

    installed is true, false, or null (not known). Never report null as installed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`action`	No		preflight
`account_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 18, 2026

TDQS

A4.8/5.0

Behavior5/5

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

This goes well beyond the annotations by disclosing exactly what each action does and does not probe, e.g., 'status ... does not probe /account.' It also explains the tri-state semantics of `installed` and warns not to report null as installed, giving the agent nuanced behavioral knowledge the annotations cannot convey.

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 summary line is front-loaded, followed by a compact indented breakdown of each action. Every sentence contributes either a parameter explanation, a behavioral nuance, or a safety caveat. There is no filler or repetition.

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?

For a two-parameter read-only diagnostic tool with an output schema, the description covers the tool's purpose, all actions, both parameters, default behavior, and special null semantics. An agent has everything it needs to select the correct action and pass the right arguments.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden for both parameters, and it succeeds. It defines the three `action` values and their defaults, and explains why `account_id` matters and when to pass it. This fully compensates for the schema's lack of enumerated or described values.

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 opens with a precise statement: 'Check GetSign auth and Monday-app install state.' It then enumerates the three action modes with distinct meanings, making the tool's purpose and scope unambiguous. The title reinforces the same message without tautology.

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 clearly states which action to use for what situation: preflight probes /account when connected, status only checks the token, and install_state requires account_id for never-connected accounts. It does not explicitly contrast with a sibling like getsign_status, so a full 5 for exclusions/alternatives is not warranted, but the operational guidance is clear.

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

All GetSign MCP 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.

Resources

Need Help?