Skip to main content
Glama

API Acre

by com.apiacre
OverviewDiscussionsAdmin

web.tech-fingerprint

Read-onlyIdempotent

Identify frameworks, analytics, CDNs, servers, and other website technologies from public response signals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesStructured Technology fingerprint result
metaYes
serviceYes
versionYes
request_idYesUnique request identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedOutput schema / properties / meta / properties / next_actions / items / properties / checkout_path
      Added value: +{
+  "pattern": "^/try/",
+  "type": "string"
+}
    • addedOutput schema / properties / meta / properties / next_actions / items / properties / executes_automatically
      Added value: +{
+  "const": false,
+  "type": "boolean"
+}
    • addedOutput schema / properties / meta / properties / next_actions / items / properties / handoff_path
      Added value: +{
+  "description": "Free full contract and spend-capped command handoff; reading it does not execute or purchase the follow-up.",
+  "pattern": "^/catalog/",
+  "type": "string"
+}
    • addedOutput schema / properties / meta / properties / next_actions / items / properties / handoff_payment_required
      Added value: +{
+  "const": false,
+  "type": "boolean"
+}
    • addedOutput schema / properties / meta / properties / next_actions / items / properties / maximum_atomic_usdc
      Added value: +{
+  "pattern": "^[1-9][0-9]*$",
+  "type": "string"
+}
    • addedOutput schema / properties / meta / properties / next_actions / items / properties / sample_path
      Added value: +{
+  "pattern": "^/samples/",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedOutput schema / properties / meta / properties / next_actions / items / required
      Previous value: -[
-  "service",
-  "title",
-  "reason",
-  "method",
-  "path",
-  "price",
-  "input_template",
-  "use_output",
-  "authorization_required"
-]New value: +[
+  "service",
+  "title",
+  "reason",
+  "method",
+  "path",
+  "price",
+  "input_template",
+  "use_output",
+  "handoff_path",
+  "checkout_path",
+  "sample_path",
+  "maximum_atomic_usdc",
+  "handoff_payment_required",
+  "executes_automatically",
+  "authorization_required"
+]
  2. Changed1 schema field changed
    • changedOutput schema / properties / data / properties / poweredBy / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  3. Changed2 schema fields changed
    • addedOutput schema / properties / meta / properties / next_actions
      Added value: +{
+  "description": "Optional separately priced follow-up calls. Each action requires a new payment challenge and explicit buyer authorization.",
+  "items": {
+    "properties": {
+      "authorization_required": {
+        "const": true,
+        "type": "boolean"
+      },
+      "input_template": {
+        "description": "Client-side template only: $request refers to the original input, $result to this response, and $json(...) serializes its argument. The server does not execute the follow-up.",
+        "type": "object"
+      },
+      "method": {
+        "const": "POST",
+        "type": "string"
+      },
+      "path": {
+        "pattern": "^/v1/",
+        "type": "string"
+      },
+      "price": {
+        "pattern": "^\\$[0-9]+",
+        "type": "string"
+      },
+      "reason": {
+        "type": "string"
+      },
+      "service": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      },
+      "use_output": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "service",
+      "title",
+      "reason",
+      "method",
+      "path",
+      "price",
+      "input_template",
+      "use_output",
+      "authorization_required"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedOutput schema / properties / meta / required
      Previous value: -[
-  "duration_ms",
-  "cached",
-  "sources",
-  "warnings"
-]New value: +[
+  "duration_ms",
+  "cached",
+  "sources",
+  "warnings",
+  "next_actions"
+]
  4. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds that it uses 'public response signals,' which is useful context, but it does not describe output format, limitations, or error behavior. This is consistent with annotations, no contradiction.

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, focused sentence that is front-loaded with the action verb and specific details. It contains no redundant or extraneous information, earning a perfect score for conciseness.

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 the tool's simplicity (one parameter, output schema, and safety annotations), the description provides sufficient context about its function and data source ('public response signals'). It could mention limitations or use cases, but these are not critical for such a straightforward tool.

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%, so the description must compensate for the undocumented URL parameter. However, it only mentions 'website technologies' and does not explicitly state that a URL is required or explain any constraints beyond the schema's property name and format. The parameter is minimally self-evident but the description adds little value.

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 clearly states the tool identifies frameworks, analytics, CDNs, servers, and other website technologies, using a specific verb (Identify) and resource. It distinguishes from sibling tools like web.extract or web.metadata, which focus on content or metadata extraction.

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 implies usage for discovering a website's technology stack but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions. The name and purpose make it reasonably obvious, but there is no explicit context or comparison.

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

All API Acre 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