7IT Solutions

Ask 7IT Solutions a question

ask_7it

Read-only

Use this when the user has a specific question for 7IT that describe_studio does not answer. Ask 7IT Solutions, a solo senior software studio, a question about whether it fits a project, what a first phase could cover, how engagements run, or what the client owns. Answers come only from 7IT's published profile and contain no prices or commitments; questions that need a quote are passed to our team, which replies directly.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "question": "<question>"
    },
    "name": "ask_7it"
  }
}

Input Schema

Name	Required	Description	Default
`question`	Yes	The question, in plain words. Include the business context that matters, for example the platform, the systems involved or what the app does.

Output Schema

Name	Required	Description
`answer`	Yes	Answer from the published profile, or null when it was forwarded without one
`contact`	Yes
`forwarded_to_founder`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "answer": {
+      "description": "Answer from the published profile, or null when it was forwarded without one",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "contact": {
+      "type": "string"
+    },
+    "forwarded_to_founder": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "answer",
+    "forwarded_to_founder",
+    "contact"
+  ],
+  "type": "object"
+}

AddedOct 1, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well past the annotations (readOnly/openWorld/non-idempotent) by disclosing the knowledge source ('only from 7IT's published profile'), the content boundary ('no prices or commitments'), and the escalation path ('passed to our team, which replies directly'). This is exactly the non-obvious behavior an agent needs before promising an answer to a user.

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: trigger condition first, topical scope second, output limits and escalation third. No filler; the gating clause is front-loaded where an agent will read it.

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?

Output schema exists so return shape needn't be described; what remains — when to call it, what it can and cannot answer, and what happens when it can't — is all covered. Nothing an agent needs to invoke it responsibly is missing.

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

Parameters4/5

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

With one parameter at 100% schema coverage the baseline is 3; the description adds value by naming the question categories that yield good answers (fit, first phase, engagement model, ownership). It doesn't restate the length limit or phrasing guidance, which the schema already handles.

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?

Specific verb+resource: 'Ask 7IT Solutions ... a question', with the topical scope enumerated (project fit, first phase, engagements, client ownership). It explicitly distinguishes itself from the sibling describe_studio, so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

States the selection condition precisely ('when the user has a specific question for 7IT that describe_studio does not answer') and names the alternative that takes precedence. It also implies the exclusion: quote-needing questions get forwarded rather than answered here.

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

All 7IT Solutions tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?