Skip to main content
Glama
Sign In
M-Pineapple

Msty Admin MCP

by M-Pineapple
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ask Frontier

ask_frontier

Send one hard question to a frontier cloud model (Cursor, Grok, or Claude) and get the answer text back. Use it to offload a single tough query, then stop.

Instructions

Send one hard question to Cursor (default), Grok or Claude and return the answer. Stay as this one tool. Use escalate_if_needed when you also want a reason field. Calls the network. Needs the matching API key. Call once, then stop. Returns the answer text.

Input Schema

NameRequiredDescriptionDefault
freshNoSet true to start a new cloud chat instead of continuing the last session. Default false.
providerNoCloud provider: cursor, grok or claude. Default cursor.
questionYesQuestion for the cloud model.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv6.2.1
    • addedInput schema / properties / fresh / description
      Added value: +"Set true to start a new cloud chat instead of continuing the last session. Default false."
    • addedInput schema / properties / provider / description
      Added value: +"Cloud provider: cursor, grok or claude. Default cursor."
    • addedInput schema / properties / question / description
      Added value: +"Question for the cloud model."
  2. Changed2 schema fields changedv6.2.0
    • addedInput schema / properties / fresh
      Added value: +{
+  "default": false,
+  "title": "Fresh",
+  "type": "boolean"
+}
    • addedInput schema / properties / provider
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Provider"
+}
  3. Addedv6.1.5

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true and idempotentHint=false, but the description adds non-obvious context: it calls the network, requires the matching API key, and should be invoked once rather than repeatedly. It does not mention cost, rate limits, or latency, which for a paid frontier-model call would be the last missing piece.

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?

Front-loaded with the core action and sized to about five short sentences with no filler. 'Stay as this one tool' is clipped enough to be ambiguous, slightly blunting an otherwise efficient structure.

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, yet the description still notes it returns answer text, and it covers the operational essentials an agent needs: provider default, auth requirement, network access, the sibling alternative, and the stop-after-one-call rule.

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%, so all three parameters (question, provider, fresh) are already documented. The description only reinforces the provider default ('Cursor (default)') and adds nothing about session semantics for 'fresh'; baseline 3 applies.

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?

States a specific verb+resource (send one hard question to Cursor/Grok/Claude) and explicitly names the default provider. It also distinguishes itself from the nearest sibling, escalate_if_needed, so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

Names the alternative explicitly ('Use escalate_if_needed when you also want a reason field') and gives a hard usage constraint ('Call once, then stop' / 'Stay as this one tool') that prevents provider-chaining. Both when-to-use and when-not-to-use are present.

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