agentView

Search Resources

search

Read-onlyIdempotent

Searches agentView resources by keyword: documentation, server status, your account, your displays and the API catalog. Returns ranked resource URIs with snippets to read via fetch. Unauthenticated searches cover public docs only. Skip when you already know the URI — call fetch directly.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results to return. Integer between 1 and 20 inclusive. Defaults to 5.
`query`	No	Free-text search terms. Examples: a display name, 'account', 'OAuth', 'status'. At least one of query or resource_type should be provided.
`resource_type`	No	Restricts results to a specific resource category. Must be one of: 'all', 'documentation', 'status', 'account', 'display', 'api'. Defaults to 'all' when omitted.
`session_request_id`	No	Session handle from create_auth_session; pass it on every authenticated call.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No
`query`	No
`results`	No
`resourceType`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedAug 31, 2026

addedInput schema / properties / session_request_id

Added value: +{
+  "description": "Session handle from create_auth_session; pass it on every authenticated call.",
+  "type": "string"
+}

Changed10 schema fields changedJun 2, 2026
- changedOutput schema / properties / count / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
- changedOutput schema / properties / query / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / resourceType / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / requiresAuthentication / type
```
Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / snippet / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / title / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / type / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / uri / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / type
```
Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
```
- changedOutput schema / properties / results / type
```
Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
```

Changed12 schema fields changedMay 23, 2026

removedInput schema / properties / access_token

Removed value: -{
-  "default": null,
-  "description": "Optional JWT access token for authentication. Pass the token returned by get_auth_session when your MCP client does not send it as an Authorization: Bearer HTTP header automatically.",
-  "type": [
-    "string",
-    "null"
-  ]
-}

removedInput schema / properties / limit / default
```
Removed value: -null
```
addedInput schema / properties / limit / maximum
```
Added value: +20
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -[
-  "integer",
-  "null"
-]New value: +"integer"

removedInput schema / properties / query / default
```
Removed value: -null
```

changedInput schema / properties / query / type

Previous value: -[
-  "string",
-  "null"
-]New value: +"string"

removedInput schema / properties / resource_type / default
```
Removed value: -null
```

addedInput schema / properties / resource_type / enum

Added value: +[
+  "all",
+  "documentation",
+  "status",
+  "account",
+  "display",
+  "api"
+]

changedInput schema / properties / resource_type / type

Previous value: -[
-  "string",
-  "null"
-]New value: +"string"

removedInput schema / properties / session_request_id

Removed value: -{
-  "default": null,
-  "description": "Optional session request ID returned by create_auth_session. Pass this instead of access_token for simpler, more reliable authentication when searching private resources.",
-  "type": [
-    "string",
-    "null"
-  ]
-}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "query": {
+      "type": "string"
+    },
+    "resourceType": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "properties": {
+          "requiresAuthentication": {
+            "type": "boolean"
+          },
+          "snippet": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          },
+          "uri": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedMay 8, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds meaningful behavior: results are ranked URIs with snippets, and unauthenticated searches only cover public documentation. This is useful context beyond 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?

Three sentences with no filler. The core action is stated first, then return format, auth caveat, and the fetch alternative. Every sentence earns its place.

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?

Given the output schema, fully documented parameters, and annotations, the description provides all necessary context: scope, result format, auth behavior, and an explicit alternative for when the URI is already known. Nothing essential is missing.

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 the input schema already documents all four parameters fully. The description does not add parameter-specific details beyond restating the resource categories, which keeps it at the baseline for well-covered schemas.

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 names a specific verb and resource ('searches agentView resources by keyword') and enumerates the exact categories covered: documentation, server status, account, displays, and API catalog. It clearly distinguishes the tool from the sibling search_public_apis and fetch tools.

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

Usage Guidelines4/5

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

The description explicitly tells the agent when not to use this tool: 'Skip when you already know the URI — call fetch directly.' It also gives the search context (agentView resources) and the unauth/public-docs limitation, though it does not explicitly contrast with search_public_apis or search_store_templates.

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

All agentView tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Most tools map cleanly to distinct resource-action pairs (displays, organizations, assets, data slots, store templates, auth). A few clusters like the get_store_template_* family and the auth/session tools could still confuse an agent, but their descriptions are explicit enough to separate them.

Naming Consistency4/5

The dominant pattern is consistent verb_noun snake_case (list_*, get_*, create_*, delete_*, send_*, set_*, manage_*). Deviations like fetch, search, authenticate, logout, and pair_by_code are understandable but break the otherwise uniform naming scheme.

Tool Count1/5

With 57 tools this server far exceeds the 50+ threshold, creating an extreme tool-set size for an MCP server. Even though the underlying platform is feature-rich, the sheer number of tools heavily taxes context and selection.

Completeness4/5

The surface covers display, organization, asset, data slot, store template, auth, API key, and licensing lifecycles in impressive depth. Minor gaps exist, such as no delete operation for display categories and no reboot/power control for displays.

Resources

Need Help?