Skip to main content
Glama

agentView

by de.agentview
OverviewDiscussionsAdmin

Submit Feedback

submit_feedback

Sends the user's feedback, feature request or bug report about agentView itself (not display content) for later review. You may also ask for it once, unprompted, right after the user has seen their first content on a screen - what they expected, what is missing - since nothing else in the product asks them; ask once and take no for an answer. Confirm the exact wording with the user before sending and send only their own words; optional sentiment. There is no automatic reply. Requires content scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesThe user's verbatim feedback text (max 2000 characters). Pass what the user actually said; do not paraphrase or add your own commentary.
sentimentNoOptional overall sentiment of the feedback. Set only when the user's tone is clear; omit if unsure.
access_tokenNoOptional bearer token; prefer session_request_id.
session_request_idNoSession handle from create_auth_session; pass it on every authenticated call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  2. Changed3 schema fields changed
    • changedInput schema / properties / access_token / description
      Previous value: -"Optional JWT access token for authentication."New value: +"Optional bearer token; prefer session_request_id."
    • changedInput schema / properties / session_request_id / description
      Previous value: -"Optional session request ID returned by create_auth_session. Preferred over access_token."New value: +"Session handle from create_auth_session; pass it on every authenticated call."
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "id": {
-      "type": [
-        "integer",
-        "null"
-      ]
-    },
-    "status": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed2 schema fields changed
    • changedOutput schema / properties / id / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • changedOutput schema / properties / status / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  4. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations cover safety profile (readOnly=false, destructive=false, idempotent=false). Description adds valuable context the annotations cannot: no automatic reply, confirm exact wording before sending, send only user's own words. Doesn't disclose what happens on error or rate limits, but for a feedback submission the write semantics are well-covered.

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 what and scope. The unsolicited-ask guidance is important but slightly buries the core usage. Overall efficient with no filler, though the middle clause about asking unprompted is a longer tangent.

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 (so return values needn't be described), annotations cover safety profile, and the description provides the behavioral, usage, and scope context needed to invoke correctly. Covers the unusual agent-specific concern (when to proactively ask) that no other field addresses.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds meaningful constraints beyond the schema: 'send only their own words' reinforces the message parameter's verbatim requirement, and 'optional sentiment' clarifies the sentiment parameter's optionality. Slight uplift for reinforcing these semantic constraints.

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?

Specific verb (sends) + resource (user's feedback/feature request/bug report) + critical scope qualifier ('about agentView itself, not display content'). The disambiguation from display content is essential given siblings like broadcast_content, send_html, and send_url that all deal with display content.

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?

Explicit when-to-use ('right after the user has seen their first content on a screen'), when-not-to-use ('not display content'), frequency constraint ('ask once, take no for an answer'), and the scope prerequisite ('Requires content scope'). Nothing is left to inference.

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

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