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

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes
cursorNoOpaque next_cursor from the previous search page. Use with unchanged query, filters, and limit.
filtersYes
organization_idNoPlatform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. 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"
+}
  3. 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"
+  }
+]
  4. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds real value beyond them: the grouped studies[] shape, the index_status lifecycle values, and the explicit note that no generated prose is returned, plus pagination termination behavior.

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?

Three tight sentences, front-loaded with purpose, then result shape, then pagination. No filler, though the result-shape sentence is dense and could be trimmed since an output schema exists.

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

Completeness4/5

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

Given an output schema exists, return values needn't be described, yet the description usefully characterizes the grouping and pagination. The main gap is filter/query semantics for a tool whose schema coverage is low, but overall it is adequate for correct invocation.

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 must compensate, but it only clarifies the cursor parameter (next_cursor) and names query/filters/limit without explaining their semantics. It says nothing about study_ids, content_types, or the date-range filters, leaving the nested filter object opaque.

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?

States a specific verb+resource ('Search one or more studies') and describes the result shape. However, it never distinguishes itself from close siblings like answer_research or list_studies, so an agent must infer when this cross-study search differs from those.

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

Usage Guidelines3/5

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

Provides strong continuation guidance (pass next_cursor back with the same query, filters, and limit; stop when null), which is genuinely useful usage context. But it gives no when-to-use/when-not guidance relative to sibling tools such as answer_research or list_studies.

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