Skip to main content
Glama

agentee

by art.allover
OverviewDiscussionsAdmin

List my submissions

designer_submissions
Read-onlyIdempotent

The user's Studio publications in moderation: in review / in catalog / needs changes. Args: limit?.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax submissions to return (default 20, max 100).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
pitchNoDesigner-program pitch to relay to the user — present when is_partner is false.
is_partnerNo
how_to_joinNoHow to join the designer program — present when is_partner is false.
submissionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Max submissions to return (default 20, max 100)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "how_to_join": {
+      "description": "How to join the designer program — present when is_partner is false.",
+      "type": "string"
+    },
+    "is_partner": {
+      "type": "boolean"
+    },
+    "note": {
+      "type": "string"
+    },
+    "pitch": {
+      "description": "Designer-program pitch to relay to the user — present when is_partner is false.",
+      "type": "string"
+    },
+    "submissions": {
+      "items": {
+        "properties": {
+          "design_name": {
+            "type": "string"
+          },
+          "id": {
+            "type": "integer"
+          },
+          "status": {
+            "description": "in review | in catalog | needs changes",
+            "type": "string"
+          },
+          "submitted_at": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds context about the moderation statuses but does not disclose any additional behavioral traits (e.g., pagination, rate limits). This is adequate given 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (two short sentences) and front-loaded with the tool's purpose. However, the second sentence is a bit cryptic ('Args: limit?') and could be more readable.

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

Completeness3/5

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

The description explains the output (moderation statuses), and an output schema exists (per context signals). However, it lacks details on ordering or filtering, and does not differentiate from similar tools like designer_designs. It is minimally complete for a simple read-only list tool.

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?

The input schema covers the single 'limit' parameter thoroughly (default 20, max 100). The description only mentions 'Args: limit?' which adds no new information beyond the schema. With 100% schema coverage, the baseline score of 3 is appropriate.

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 clearly states it lists the user's Studio publications currently in moderation, enumerating the specific statuses (in review, in catalog, needs changes). This distinguishes it from sibling tools like designer_designs (which likely lists all designs) or designer_uploads (uploads).

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 is provided on when to use this tool versus siblings. There is no explicit 'when-to-use' or 'when-not-to-use' advice, limiting the agent's ability to decide between this and similar list tools.

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

All agentee 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