Skip to main content
Glama

User Intuition

by ai.userintuition
OverviewDiscussionsAdmin

Search Research

search_research
Read-onlyIdempotent

Search one or more studies. Results are grouped under studies[] with each study_id, index_status (ready, updating, or not_indexed), latest_report_id, indexed_report_id, and matching canonical content. No generated prose is returned. Pass next_cursor back with the same query, filters, and limit to continue; stop when it is null.

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
cursorNoOpaque next_cursor from the previous search page. Use with unchanged query, filters, and limit.
filtersYes
organization_idNoOrganization for this operation and billing. Use list_organizations to choose an active membership.

Output Schema

NameRequiredDescriptionDefault
resultYesRanked canonical study and report JSON. Generated prose is never returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / organization_id / description
      Previous value: -"Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet."New value: +"Organization for this operation and billing. Use list_organizations to choose an active membership."
  2. Changed3 schema fields changed
    • addedInput schema / properties / cursor / anyOf
      Added value: +[
+  {
+    "maxLength": 32768,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / cursor / description
      Previous value: -"Reserved for future pagination; only null is supported."New value: +"Opaque next_cursor from the previous search page. Use with unchanged query, filters, and limit."
    • removedInput schema / properties / cursor / type
      Removed value: -"null"
  3. Changed1 schema field changed
    • addedInput schema / properties / organization_id
      Added value: +{
+  "description": "Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}
  4. Changed18 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / filters / properties / research_date_to / $ref
      Removed value: -"#/properties/filters/properties/research_date_from"
    • addedInput schema / properties / filters / properties / research_date_to / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
    • addedInput schema / properties / filters / properties / research_date_to / type
      Added value: +"string"
    • addedInput schema / properties / filters / properties / study_ids / items / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / properties / result / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / result / properties / studies / items / additionalProperties
      Previous value: -trueNew value: +{}
    • removedOutput schema / properties / result / properties / studies / items / properties / indexed_report_id / $ref
      Removed value: -"#/properties/result/properties/studies/items/properties/latest_report_id"
    • addedOutput schema / properties / result / properties / studies / items / properties / indexed_report_id / type
      Added value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / result / properties / studies / items / properties / results / items / additionalProperties
      Previous value: -trueNew value: +{}
    • addedOutput schema / properties / result / properties / studies / items / properties / results / items / properties / content / propertyNames
      Added value: +{
+  "type": "string"
+}
    • removedOutput schema / properties / result / properties / studies / items / properties / results / items / properties / interview_id / $ref
      Removed value: -"#/properties/result/properties/studies/items/properties/latest_report_id"
    • addedOutput schema / properties / result / properties / studies / items / properties / results / items / properties / interview_id / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / result / properties / studies / items / properties / results / items / properties / report_id / $ref
      Removed value: -"#/properties/result/properties/studies/items/properties/latest_report_id"
    • addedOutput schema / properties / result / properties / studies / items / properties / results / items / properties / report_id / type
      Added value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / result / properties / studies / items / properties / results / items / properties / research_period / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "end": {
-        "$ref": "#/properties/result/properties/studies/items/properties/results/items/properties/report_generated_at"
-      },
-      "start": {
-        "$ref": "#/properties/result/properties/studies/items/properties/results/items/properties/report_generated_at"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "end": {
+        "description": "ISO 8601 timestamp.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "start": {
+        "description": "ISO 8601 timestamp.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  5. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds meaningful behavior beyond annotations by explaining the grouped studies[] result shape, index_status values, absence of generated prose, and cursor continuation rules.

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 front-loaded, compact, and avoids filler. The result-field list is dense but operationally useful, and the pagination rule is clearly stated.

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 output schema exists, so the description need not fully document return values, and it usefully covers result grouping and pagination. However, for a tool with five parameters and nested filters, it leaves key parameter semantics and when-to-use guidance under-explained.

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

Parameters2/5

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

Schema description coverage is only 40%, so the description needs to compensate, but it explains only cursor reuse with unchanged query, filters, and limit. It does not clarify query semantics, the nested filter fields such as study_ids and content_types, date-range filtering, or organization_id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: "Search one or more studies," and clarifies that matching canonical content is returned. It is clear enough to distinguish a search operation from a simple list, but it does not explicitly name sibling tools or contrast itself with alternatives such as answer_research or list_studies.

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?

The description does not state when to use this tool versus alternatives, nor does it give exclusions beyond noting that no generated prose is returned. Cursor continuation guidance is present, but that is pagination behavior rather than tool-selection guidance.

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

All User Intuition 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