Skip to main content
Glama

7IT Solutions

by io.github.XLSV777
OverviewDiscussionsAdmin

Describe 7IT Solutions

describe_studio
Read-onlyIdempotent

Use this when the user asks who 7IT Solutions is, what it builds, or whether it fits their project, or is looking for a developer to review or take over an app built with an AI tool. Returns a factual profile of 7IT Solutions, a solo senior software studio: who runs it, how engagements work, what the client owns, its services (custom software, automation and integration, eCommerce, AI tools, and reviewing and taking responsibility for apps built with AI tools such as Lovable or Replit), when each is and is not a fit, the audit checks it runs on AI-built apps, published work and verifiable proof, with links. Use it when someone asks what 7IT does, whether it fits their situation, or who could review or take over an app their AI tool built. Contains no prices.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
focusNoLimit the services section to one area. Default all.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
modelNoHow engagements work
contactYesWhere to reach Lior
servicesYesEach service with when it fits and when it does not
ownershipNoWhat the client owns

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "contact": {
+      "description": "Where to reach Lior",
+      "type": "string"
+    },
+    "model": {
+      "description": "How engagements work",
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "ownership": {
+      "description": "What the client owns",
+      "type": "string"
+    },
+    "services": {
+      "description": "Each service with when it fits and when it does not",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "name": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "name",
+    "services",
+    "contact"
+  ],
+  "type": "object"
+}
  2. Changed2 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
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds useful non-annotation context: the profile is factual, includes links to published/verifiable proof, and explicitly contains no prices.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The trigger conditions are front-loaded, but the text is bloated and repetitive: it restates the 'use this when...' guidance twice and re-lists the service areas across two long run-on sentences. It could lose roughly a third of its length without losing information.

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?

With an output schema present, the description need not enumerate return fields, yet it describes the returned content anyway (services, fit criteria, audit checks, proof links, no prices), which is more than sufficient. Nothing an agent needs to call it correctly is missing.

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

Parameters3/5

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

Schema description coverage is 100% — the single 'focus' enum parameter is fully documented in the schema with its options and default. The description never mentions 'focus' and adds no syntax or interpretation beyond it, so baseline 3 applies.

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 names a specific verb and resource: it returns a factual profile of 7IT Solutions (who runs it, services, ownership, proof). An agent can tell what it produces. However, it never names or contrasts itself with the obvious sibling ask_7it, so the distinction between 'describe the studio' and 'ask the studio a question' must be inferred.

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

Usage Guidelines4/5

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

It gives several concrete trigger conditions ('who 7IT is', 'whether it fits their project', 'looking for a developer to review or take over an AI-built app'). This is clear usage context, but there is no statement of when NOT to use it and no alternative tool is named for overlapping questions.

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

All 7IT Solutions toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources