Skip to main content
Glama

FolioFact

by com.foliofact
OverviewDiscussionsAdmin

Search funds, stocks, and insiders

search
Read-onlyIdempotent

Bounded cross-domain search: funds by name, stocks by ticker/name, and insider transactions by owner. The same scopes the web search uses. A blank or missing query returns empty buckets, mirroring GET /api/v1/search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSearch query (fund names, tickers, insider names).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
resultsYes
provenanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / results / properties / stocks / items / properties / listing
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "disclosure_note": {
+          "type": "string"
+        },
+        "event_type": {
+          "enum": [
+            "ipo",
+            "direct_listing",
+            "spin_off"
+          ],
+          "type": "string"
+        },
+        "listed_on": {
+          "format": "date",
+          "type": "string"
+        },
+        "recently_listed": {
+          "type": "boolean"
+        },
+        "source_url": {
+          "format": "uri",
+          "type": "string"
+        }
+      },
+      "required": [
+        "listed_on",
+        "event_type",
+        "recently_listed",
+        "source_url",
+        "disclosure_note"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedOutput schema / properties / results / properties / stocks / items / required
      Previous value: -[
-  "ticker",
-  "name"
-]New value: +[
+  "ticker",
+  "name",
+  "listing"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, and non-destructive behavior; the description adds the important edge-case behavior that blank or missing queries return empty buckets. It also states the bounded scope, echoing the closed-world annotation, and contains no contradiction with 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 deliver scope, domain mapping, and empty-query behavior with no filler. The most important differentiator, bounded cross-domain search, is front-loaded.

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?

For a one-optional-parameter search tool with a rich output schema and strong annotations, the description covers purpose, scope, domain mapping, and the edge case. There is no essential context missing for correct invocation, though sibling-selection guidance could be stronger.

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

Parameters5/5

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

The schema documents the single query parameter with examples, and the description goes further by mapping query forms to each domain: funds by name, stocks by ticker/name, and insider transactions by owner. It also clarifies the optional-parameter case with the empty-bucket behavior, so parameter semantics are fully covered.

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 the search verb, enumerates the three resources (funds, stocks, and insider transactions), and states the fields each can be queried by. This makes it easy to distinguish from sibling getters like get_fund, get_stock, and insider_feed.

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?

It clearly identifies the tool as a cross-domain search entry point with the same scopes as web search, so an agent can infer when a broad query is intended. However, it never says when to prefer the specific sibling tools instead, leaving exclusion guidance implicit.

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

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