OASF 0.6.0 MCP: tool parameters - possible to add?

[sfph]

Hi there!

Prior to 0.6.0, we have pushed MCP records with a tool_configuration like the below. I see that tools, prompts and resources are now stripped out and the tool_configuration paragraph has been removed. Prompts and resources look easy to translate. For prompts, 'content' becomes 'command'; for resources, 'url' becomes 'uri'. But I don't see an equivalent for the 'parameters' object under tools, and it looks like it could be useful, if a tool does require parameters. Would it be possible to add this parameters object to tools?

Example current MCP Server record.

      "tool_configuration": {
                     "tools": [
                        {
                           "name": "get-forecast",
                           "description": "Retrieves detailed weather forecast for a specified US location.",
                           "parameters": [
                              {
                                 "name": "latitude",
                                 "type": "number",
                                 "description": "Latitude of the location (-90 to 90).",
                                 "required": true
                              },
                              {
                                 "name": "longitude",
                                 "type": "number",
                                 "description": "Longitude of the location (-180 to 180).",
                                 "required": true
                              }
                           ]
                        },
                        {
                           "name": "search-data",
                           "description": "Search through available data records.",
                           "parameters": [
                              {
                                 "name": "query",
                                 "type": "string",
                                 "description": "Search query string.",
                                 "required": true
                              },
                              {
                                 "name": "limit",
                                 "type": "number",
                                 "description": "Maximum number of results to return.",
                                 "required": false
                              }
                           ]
                        },
                        {
                           "name": "get-alerts",
                           "description": "Retrieves active weather alerts for a specified US state.",
                           "parameters": [
                              {
                                 "name": "state",
                                 "type": "string",
                                 "description": "Two-letter US state code (e.g., CA, NY).",
                                 "required": true
                              }
                           ]
                        }
                     ],
                     "prompts": [
                        {
                           "name": "help",
                           "content": "Type 'help' for a list of available commands and tools, or use the /tools endpoint to discover tool capabilities."
                        },
                        {
                           "name": "greeting",
                           "content": "Hello! I can help you with weather information and forecasts."
                        },
                        {
                           "name": "error",
                           "content": "An error occurred while fetching weather data. Please check your input and try again."
                        },
                        {
                           "name": "welcome",
                           "content": "Welcome to the MCP Weather Server. Use the available tools to get weather forecasts and alerts."
                        }
                     ],
                     "resources": [
                        {
                           "name": "documentation",
                           "url": "https://modelcontextprotocol.io/docs/mcp-weather",
                           "description": "Official documentation for the MCP Weather Server."
                        },
                        {
                           "name": "examples",
                           "url": "https://modelcontextprotocol.io/examples/mcp-weather",
                           "description": "Example requests and responses for using the server."
                        },
                        {
                           "name": "api-docs",
                           "url": "https://api.0p2lqg.com/docs",
                           "description": "API documentation and reference."
                        }
                     ]
                  }

[ramizpolic]

The reason why we removed this is because we did not want to fully clone the MCP schema into OASF. In addition, the tools (and other property) information can be retrieved directly from URL field of the MCP server. For simplicity, all MCP server information can be gathered once the server is running and has an accessible URL, which means that OASF could simply provide ways to interact with the server (via URL) or optionally to also deploy the server (as to get the URL).

[nishantapatil3]

I would agree to have tools_configuration optional, as we currently do it on SaaS, suggestion is to have tools_configuration and corresponding tools, prompts, resources as its children. This helps in migration records from 0.3.1 to 0.6.0 if required in the future.

[muscariello]

tools_conf was a mistake and was reverted because it replicates the content of the spec. Which is already available in the server itself.

MCP registry does not replicate config data in the registry. It's linked.

See https://github.com/modelcontextprotocol/registry

[nandu-gh]

Apart from the migration requirement, we also have a requirement to parse the complete tool configuration and use it as part of semantic search experience. This requires to understand tool commands/parameters and not just tool name & description.

We also need to support the workflows of letting users build or generate an OASF record from the DirManager UI. A developer connecting to a running MCP server from their IDE and introspecting the configuration is one thing but asking users logged into https://agent-directory.outshift.com connect to a remote MCP server is not feasible from a security point of view.

We could define the tool_configuration" -> "tools" -> [ ] -> parameters as an optional JSON array element in the MCP schema extension.

[sfph]

Hi @muscariello, could you let us know where this is? Simply adding a parameters object would let users gracefully include the information under the MCP servers tools block.

[nandu-gh]

@lgecse , @muscariello Can we add the parameters object to the MCP server module (extension)? This is similar to the "args" field we have in the LLM Prompt module (extension)