Skip to main content
Glama
Sign In

Parse

by gl.parse.mcp
OverviewDiscussionsAdmin

Changes that are made in Parse itself

parse_app_link
Read-onlyIdempotent

Use when the user asks to change billing, invite or remove members, delete a brand, connect an account, or add a topic with Parse's review of its wording. An assistant cannot make these changes: this returns the link to the right place in Parse and one sentence saying why. Give the user the link. To add a topic in the user's exact words, call parse_add_topic instead.

Input Schema

NameRequiredDescriptionDefault
actionYesbilling: plan or payment. members: invite or remove people. delete_brand: remove a brand. connect_account: connections and assistant permissions. add_topic: add a topic in the app, where Parse reviews its wording (the value keeps its old name: it adds a topic, never a market).
brandSlugNoThe brand's slug or its name. Omit it to use the workspace's own brand.

Output Schema

NameRequiredDescriptionDefault
urlYes
whyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"billing: plan or payment. members: invite or remove people. delete_brand: remove a brand. connect_account: connections and assistant permissions. add_market: add a topic in the app, where Parse reviews its wording (the value keeps its old name: it adds a topic, never a market)."New value: +"billing: plan or payment. members: invite or remove people. delete_brand: remove a brand. connect_account: connections and assistant permissions. add_topic: add a topic in the app, where Parse reviews its wording (the value keeps its old name: it adds a topic, never a market)."
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "billing",
-  "members",
-  "delete_brand",
-  "connect_account",
-  "add_market"
-]New value: +[
+  "billing",
+  "members",
+  "delete_brand",
+  "connect_account",
+  "add_topic"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / action / description
      Previous value: -"billing: plan or payment. members: invite or remove people. delete_brand: remove a brand. connect_account: connections and assistant permissions. add_market: add a topic to track."New value: +"billing: plan or payment. members: invite or remove people. delete_brand: remove a brand. connect_account: connections and assistant permissions. add_market: add a topic in the app, where Parse reviews its wording (the value keeps its old name: it adds a topic, never a market)."
  3. Changed1 schema field changed
    • changedInput schema / properties / action / description
      Previous value: -"billing: plan or payment. members: invite or remove people. delete_brand: remove a brand. connect_account: connections and assistant permissions. add_market: add a need to track."New value: +"billing: plan or payment. members: invite or remove people. delete_brand: remove a brand. connect_account: connections and assistant permissions. add_market: add a topic to track."
  4. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the crucial behavioral fact that the assistant cannot perform these changes and instructs the agent to hand the link to the user, which is not derivable from the annotations.

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?

Four short sentences, front-loaded with the trigger, then the effect, then the agent instruction ('Give the user the link'), then the disambiguation. No sentence is redundant given the routing decision the agent must make.

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 routing/link tool with an output schema present, the description supplies everything the agent needs: trigger conditions, the fact that no mutation occurs, the expected artifact (a link), and the sibling alternative. Return-value detail is correctly left to the output schema.

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% and the enum values are already documented per-value in the schema, so the baseline is 3. The description enumerates the same action categories but adds no syntax or format detail beyond what the schema already states, and it does not mention brandSlug at all.

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 states a specific outcome (returns a link to the right place in Parse plus one sentence of rationale) and delimits the exact action set it covers. An agent can distinguish it from siblings like parse_add_topic without opening the schema, because the description names the alternative explicitly.

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?

It opens with an explicit trigger ('Use when the user asks to change billing, invite or remove members, delete a brand, connect an account, or add a topic...') and names the branch condition for the alternative tool ('To add a topic in the user's exact words, call parse_add_topic instead'). Guidance on when-not-to-use is present, not merely implied.

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

All Parse toolsInspect
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