Skip to main content
Glama
Sign In
AbleSign MCP

AbleSign MCP

by MartinLoeper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_web_app

Retrieve web app details by ID. Access configuration, status, and other metadata for a specific web app.

Instructions

Get web app details.

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": {
      "web_app_id": "<web_app_id>"
    },
    "name": "get_web_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
web_app_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations provided, so the description bears full burden. It does not disclose that this is a read-only operation, nor does it mention any authentication requirements or side effects. The brief description offers no behavioral context beyond the obvious.

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?

The description is a single concise sentence, front-loaded with the action and resource. However, it could be slightly expanded with useful context without sacrificing conciseness.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema, the description lacks completeness for agent use. It does not explain when to invoke this tool, what prerequisites exist, or how it differs from similar tools. The minimal text leaves gaps in understanding.

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?

Schema description coverage is 0%, yet the description adds no meaning to the only parameter 'web_app_id'. While the parameter name is self-explanatory, the description should clarify its purpose (e.g., 'The unique identifier of the web app to retrieve').

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 clearly states the verb ('Get') and resource ('web app details'), distinguishing it from sibling tools like 'list_web_apps' which lists all, or 'create_web_app' which creates. However, it could be more specific about what 'details' includes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. There is no mention of the required 'web_app_id' to retrieve a specific item compared to listing all web apps with 'list_web_apps'.

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