Skip to main content
Glama

Oblique Markets

by markets.oblique.api
OverviewAdmin

rep_stableenrich_search

Run a bounded web search backed by public Wikimedia results; not an Exa or stableenrich.dev proxy. $0.01/call via x402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes
offsetNo

Schema Changelog

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

  1. Changed13 schema fields changed
    • removedInput schema / properties / current_company_domains
      Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "exact_match": {
-        "type": "boolean"
-      },
-      "exclude": {
-        "type": "boolean"
-      },
-      "value": {
-        "type": [
-          "string",
-          "number"
-        ]
-      }
-    },
-    "required": [
-      "value"
-    ],
-    "type": "object"
-  },
-  "maxItems": 10,
-  "type": "array"
-}
    • removedInput schema / properties / current_company_headquarters
      Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "exact_match": {
-        "type": "boolean"
-      },
-      "exclude": {
-        "type": "boolean"
-      },
-      "value": {
-        "type": [
-          "string",
-          "number"
-        ]
-      }
-    },
-    "required": [
-      "value"
-    ],
-    "type": "object"
-  },
-  "maxItems": 10,
-  "type": "array"
-}
    • removedInput schema / properties / current_company_industries
      Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "exact_match": {
-        "type": "boolean"
-      },
-      "exclude": {
-        "type": "boolean"
-      },
-      "value": {
-        "type": [
-          "string",
-          "number"
-        ]
-      }
-    },
-    "required": [
-      "value"
-    ],
-    "type": "object"
-  },
-  "maxItems": 10,
-  "type": "array"
-}
    • removedInput schema / properties / current_company_names
      Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "exact_match": {
-        "type": "boolean"
-      },
-      "exclude": {
-        "type": "boolean"
-      },
-      "value": {
-        "type": [
-          "string",
-          "number"
-        ]
-      }
-    },
-    "required": [
-      "value"
-    ],
-    "type": "object"
-  },
-  "maxItems": 10,
-  "type": "array"
-}
    • removedInput schema / properties / current_company_specialties
      Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "exact_match": {
-        "type": "boolean"
-      },
-      "exclude": {
-        "type": "boolean"
-      },
-      "value": {
-        "type": [
-          "string",
-          "number"
-        ]
-      }
-    },
-    "required": [
-      "value"
-    ],
-    "type": "object"
-  },
-  "maxItems": 10,
-  "type": "array"
-}
    • removedInput schema / properties / current_position_seniority_level
      Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "exact_match": {
-        "type": "boolean"
-      },
-      "exclude": {
-        "type": "boolean"
-      },
-      "value": {
-        "type": [
-          "string",
-          "number"
-        ]
-      }
-    },
-    "required": [
-      "value"
-    ],
-    "type": "object"
-  },
-  "maxItems": 10,
-  "type": "array"
-}
    • removedInput schema / properties / current_position_titles
      Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "exact_match": {
-        "type": "boolean"
-      },
-      "exclude": {
-        "type": "boolean"
-      },
-      "value": {
-        "type": [
-          "string",
-          "number"
-        ]
-      }
-    },
-    "required": [
-      "value"
-    ],
-    "type": "object"
-  },
-  "maxItems": 10,
-  "type": "array"
-}
    • removedInput schema / properties / person_locations
      Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "exact_match": {
-        "type": "boolean"
-      },
-      "exclude": {
-        "type": "boolean"
-      },
-      "value": {
-        "type": [
-          "string",
-          "number"
-        ]
-      }
-    },
-    "required": [
-      "value"
-    ],
-    "type": "object"
-  },
-  "maxItems": 10,
-  "type": "array"
-}
    • removedInput schema / properties / person_names
      Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "exact_match": {
-        "type": "boolean"
-      },
-      "exclude": {
-        "type": "boolean"
-      },
-      "value": {
-        "type": [
-          "string",
-          "number"
-        ]
-      }
-    },
-    "required": [
-      "value"
-    ],
-    "type": "object"
-  },
-  "maxItems": 10,
-  "type": "array"
-}
    • removedInput schema / properties / person_skills
      Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "exact_match": {
-        "type": "boolean"
-      },
-      "exclude": {
-        "type": "boolean"
-      },
-      "value": {
-        "type": [
-          "string",
-          "number"
-        ]
-      }
-    },
-    "required": [
-      "value"
-    ],
-    "type": "object"
-  },
-  "maxItems": 10,
-  "type": "array"
-}
    • addedInput schema / properties / query
      Added value: +{
+  "maxLength": 512,
+  "minLength": 1,
+  "type": "string"
+}
    • removedInput schema / properties / search_after
      Removed value: -{
-  "maxLength": 512,
-  "type": "string"
-}
    • addedInput schema / required
      Added value: +[
+  "query"
+]
  2. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It adds helpful details: the search is bounded, uses public Wikimedia results, and costs $0.01/call via x402. Yet it omits important behaviors such as read-only safety, rate limiting, failure modes, or return format, which an agent may need to handle edge cases.

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?

The description is a single dense sentence that front-loads the core action and data source, then adds the exclusion and cost. Every phrase adds value, and there is no filler, tautology, or unnecessary restructuring.

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?

For a straightforward search tool with a small schema and no output schema, this description provides essential context: what is searched (Wikimedia), how results are bounded, and what it costs. It does not describe the response shape, which is a minor gap for a search tool, but the schema already covers parameter ranges and the core usage context is sufficient.

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 0%, and the description does not explain the semantics of query, limit, or offset beyond the type/default/range information already present in the schema. The word 'bounded' hints at pagination but is not explicitly tied to limit and offset, so the description fails to compensate for the absent parameter documentation.

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 uses a specific verb and noun: 'Run a bounded web search' and identifies the backend resource 'public Wikimedia results'. It also explicitly disclaims being an Exa or stableenrich.dev proxy, which distinguishes it from sibling search tools without needing to inspect schemas.

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?

The description gives clear context by describing the tool as a bounded Wikimedia-backed search and stating what it is not ('not an Exa or stableenrich.dev proxy'). However, it does not name sibling tools or explicitly state when to prefer this over alternatives like tweets_search or web_extract, leaving the decision rule implied rather than explicit.

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

All Oblique Markets toolsInspect
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.

Resources